Summary: | sys-libs/libcxx-3.9.1: Header files have changed between ABIs. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Beutin <tb> |
Component: | Current packages | Assignee: | Alexis Ballier <aballier> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | bsd+disabled, jstein, llvm, mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=600364 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Thomas Beutin
2017-09-11 19:22:21 UTC
Created attachment 494042 [details]
build.log
# emerge -pqv '=sys-libs/libcxx-3.9.1::gentoo' [ebuild N ] sys-libs/libcxx-3.9.1 USE="-libcxxabi -libcxxrt -libunwind -static-libs {-test}" ABI_X86="32 (64) (-x32)" Could you compare headers from a failed build? Something along the lines of: $ diff -dupr /tmp/portage/sys-libs/libcxx-3.9.1/work/libcxx-3.9.1.src-abi_x86_*/include (adjust paths as necessary) (In reply to Michał Górny from comment #3) > Could you compare headers from a failed build? Something along the lines of: [...] # diff -dupr /var/tmp/portage/sys-libs/libcxx-3.9.1/work/libcxx-3.9.1.src-abi_x86_*/include Only in /var/tmp/portage/sys-libs/libcxx-3.9.1/work/libcxx-3.9.1.src-abi_x86_64.amd64/include/bits: c++config.h Only in /var/tmp/portage/sys-libs/libcxx-3.9.1/work/libcxx-3.9.1.src-abi_x86_64.amd64/include/bits: cpu_defines.h Only in /var/tmp/portage/sys-libs/libcxx-3.9.1/work/libcxx-3.9.1.src-abi_x86_64.amd64/include/bits: cxxabi_forced.h Only in /var/tmp/portage/sys-libs/libcxx-3.9.1/work/libcxx-3.9.1.src-abi_x86_64.amd64/include/bits: cxxabi_tweaks.h Only in /var/tmp/portage/sys-libs/libcxx-3.9.1/work/libcxx-3.9.1.src-abi_x86_64.amd64/include/bits: os_defines.h Only in /var/tmp/portage/sys-libs/libcxx-3.9.1/work/libcxx-3.9.1.src-abi_x86_64.amd64/include: cxxabi.h Ok, I can reproduce this both with the old version and with -9999, w/ libsupcxx backend. I suppose our code for it doesn't handle multilib well. @Thomas, unless you have a very good reason to link libc++ with libsupc++ (gcc), you can enable USE=libcxxabi or USE=libcxxrt to get libc++ building before we fix it. (In reply to Michał Górny from comment #5) [...] > @Thomas, unless you have a very good reason to link libc++ with libsupc++ > (gcc), you can enable USE=libcxxabi or USE=libcxxrt to get libc++ building > before we fix it. Thanks, sys-libs/libcxx-3.9.1[libcxxabi] fixed my issue here :) |