https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #16 from Jan Beich ---
After bug 236529 fix comment 3 shouldn't occur even if USE_GCC is dropped.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
Jan Beich changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
Jan Beich changed:
What|Removed |Added
Assignee|ge...@freebsd.org |r...@freebsd.org
CC|r.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #15 from commit-h...@freebsd.org ---
A commit references this bug:
Author: tobik
Date: Sat Mar 2 00:35:34 UTC 2019
New revision: 494349
URL: https://svnweb.freebsd.org/changeset/ports/494349
Log:
Mk/Uses/cargo.mk: Require po
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #14 from Jan Beich ---
Omitting -C linker=${CC:Q} on powerpc64 is not enough. USE_GCC machinery
implies passing -Wl,-rpath. If one of USES=cargo consumers uses libgcc_s or
libstdc++ we may end up in the same mess libgfortran inc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #13 from Jan Beich ---
(In reply to Tobias Kortkamp from comment #12)
Yes, USES=cargo should be in sync with lang/rust. Once Clang on powerpc64 is
ready we'd need to patch out cargo:rustc-link-lib=static=stdc++ (in bundled
LLVM)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #12 from Tobias Kortkamp ---
So now that every USES=cargo port has libc 0.2.49, how should we
fix the error from comment #3 on powerpc64?
Do we just add
.if ${ARCH} == powerpc64
USE_GCC?= yes
.endif
to cargo.mk and call
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #11 from commit-h...@freebsd.org ---
A commit references this bug:
Author: jbeich
Date: Thu Feb 28 18:47:42 UTC 2019
New revision: 494175
URL: https://svnweb.freebsd.org/changeset/ports/494175
Log:
USES=cargo to update libc t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
Jan Beich changed:
What|Removed |Added
URL||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
Jan Beich changed:
What|Removed |Added
See Also||https://github.com/rust-lan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
Tobias Kortkamp changed:
What|Removed |Added
Status|New |Open
--- Comment #10 from Tobias
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #9 from mikael.uran...@gmail.com ---
same error with sysutils/exa
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-gecko@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #8 from mikael.uran...@gmail.com ---
USE_GCC=7 is only useful for the bootstrap (gcc7 is hardcoded in the bootstrap
binary), gcc8 can be used for building rust. I should probably do the same
thing we do for
lang/ghc:https://svnwe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #7 from Jan Beich ---
Thanks. I agree default-linker from config.toml and -C linker from USES=cargo
should be in sync. At the moment, review D18367 proposes USE_GCC=7 for
lang/rust and this bug proposes USE_GCC=yes (lang/gcc8 af
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #6 from mikael.uran...@gmail.com ---
(In reply to Jan Beich from comment #5)
I tracked it down to https://reviews.freebsd.org/D18528, $CC is not the default
'rust linker' on ppc64 and it breaks the build. The port builds fine wit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #5 from Jan Beich ---
Is this specific to devel/rust-cbindgen or affects any USES=cargo consumer? If
the latter I'd prefer to move the quirk there, so even new ports can benefit
from it.
As review D18367 adds USE_GCC for powerp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #4 from mikael.uran...@gmail.com ---
Why does the default linker isn't used anyway? where does cc come from? it's
supposed to be gcc7 or 8 on ppc.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #3 from mikael.uran...@gmail.com ---
(In reply to Jan Beich from comment #2)
Have you tried on ppc64?
/usr/local/bin/rustc -v --crate-name build_script_build
/usr/ports/devel/rust-cbindgen/work/cbindgen-0.7.1/cargo-crates/serde-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Comment #2 from Jan Beich ---
Comment on attachment 201270
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201270
patch
> -USES=cargo
> +USES=cargo compiler:c++11-lang
Why? Is this specific to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
Jan Beich changed:
What|Removed |Added
See Also||https://github.com/rust-lan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
Jan Beich changed:
What|Removed |Added
CC||r...@freebsd.org
--- Comment #1 from J
Bugzilla Automation has asked freebsd-gecko mailing list
for maintainer-feedback:
Bug 235063: devel/rust-cbindgen: fix build on tier2 arches
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
--- Description ---
fix build on aarch64 and powerpc64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235063
Bug ID: 235063
Summary: devel/rust-cbindgen: fix build on tier2 arches
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
S
23 matches
Mail list logo
