[Bug 236900] lang/gcc8: BOOTSTRAP=off fails to build after r497254
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236900 Gerald Pfeifer changed: What|Removed |Added Flags|maintainer-feedback?(gerald | |@FreeBSD.org) | CC||d...@freebsd.org, ||ger...@freebsd.org, ||k...@freebsd.org, ||toolch...@freebsd.org Assignee|ger...@freebsd.org |andre...@freebsd.org --- Comment #1 from Gerald Pfeifer --- Does this mean we need to force bootstrapping GCC once multilibs are involved, Andreas? I'm a bit surprised this never came up around powerpc64, where we (thanks to your nice work) have been doing multilib-ing more pervasively. Of course the user base on powerpc64 is smaller, but still... Or can any of you think of a different approach? -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 236900] lang/gcc8: BOOTSTRAP=off fails to build after r497254
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236900 --- Comment #2 from Konstantin Belousov --- I successfully built without bootstrap in 11.2 jail. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
Fwd: [PATCH] D59694: [PPC64][libunwind] Fix r2 not properly restored
The below does not deal with building llvm's libunwind for WITH_LIB32= (or 32-bit powerpc targeting in general), just with targeting powerpc64 directly. Begin forwarded message: From: Nemanja Ivanovic via Phabricator Subject: [PATCH] D59694: [PPC64][libunwind] Fix r2 not properly restored Date: 2019-March-31 at 05:31:17 PDT . . . nemanjai accepted this revision. nemanjai added a comment. I don't really know much about how libunwind is tested so I can't really comment on how to write one (or the need for one). But the code looks good to me. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D59694/new/ https://reviews.llvm.org/D59694 === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 236900] lang/gcc8: BOOTSTRAP=off fails to build after r497254
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236900 --- Comment #3 from Andreas Tobler --- Ditto on -CURRENT -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 236900] lang/gcc8: BOOTSTRAP=off fails to build after r497254
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236900 Mark Millard changed: What|Removed |Added CC||marklmi26-f...@yahoo.com --- Comment #4 from Mark Millard --- (In reply to Andreas Tobler from comment #3) Looks like (system) clang rejects the option: # cc -v -print-multi-os-directory cc: error: unsupported option '-print-multi-os-directory' FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on LLVM 8.0.0) Target: x86_64-unknown-freebsd13.0 Thread model: posix InstalledDir: /usr/bin # c++ -v -print-multi-os-directory c++: error: unsupported option '-print-multi-os-directory' FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on LLVM 8.0.0) Target: powerpc64-unknown-freebsd13.0 Thread model: posix InstalledDir: /usr/bin So it appears that a successful build would have had to use the option with some gcc version instead of (system) clang. So the question translates to: what contextual difference leads to use with clang some times vs. gcc other times? Lack of a full bootstrap vs. using a full bootstrap? (Note: the powerpc64 context above is based on WITHOUT_LIB32= because of my llvm-libunwind patch testing.) -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
Problem reports for toolch...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|234232 | clang Assertion failed when building the port dev 1 problems total for which you should take action. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 236900] lang/gcc8: BOOTSTRAP=off fails to build after r497254
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236900 --- Comment #5 from Andreas Tobler --- The error mentioned in the description stems from a configure test, so we can ignore it. You'll find this error in configure stage during every gcc build, bootstrap/multilib or not. The real failure would be visible if we run the gmake -N job with N=1 and have a look into the config.log of the failing part. I bet it is the rtld which does not seem to be able to execute 32-bit bins. Due to whatever reason. On -CURRENT we had this situation for a very short time. Between r345661 and r345734. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
