This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] top-level for libvtv: use normal (not raw_cxx) target exports
- From: Jeff Law <law at redhat dot com>
- To: Michael Haubenwallner <michael dot haubenwallner at ssi-schaefer dot com>, Paolo Bonzini <bonzini at gnu dot org>, DJ Delorie <dj at redhat dot com>, Nathanael Nerode <neroden at gcc dot gnu dot org>, Alexandre Oliva <aoliva at redhat dot com>, Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Caroline Tice <cmtice at google dot com>
- Date: Thu, 25 Jun 2015 13:15:04 -0600
- Subject: Re: [PATCH] top-level for libvtv: use normal (not raw_cxx) target exports
- Authentication-results: sourceware.org; auth=none
- References: <5576F69F dot 3090205 at ssi-schaefer dot com>
On 06/09/2015 08:22 AM, Michael Haubenwallner wrote:
Hi build machinery maintainers,
since we always build the C++ compiler now, I fail to see the need to still
use RAW_CXX_TARGET_EXPORTS for libvtv.
But why is vtv special here? Wouldn't this also apply to libstdc++-v3
which would still have raw_cxx=true after your change?
It's unfortunate that David didn't document the meaning of raw_cxx...
I've read the threads from 2004 and I'm still lost.
The situation to expose the problem is:
* Use a multilib-enabled x86_64-linux box.
* Use a 64-bit (multilib-disabled) bootstrap compiler (binary image).
$ configure --enable-multilib --with-system-zlib
$ make bootstrap
When it comes to build the 32-bit libvtv, it breaks because of using
"CC=/build/prev-gcc/xgcc -m32" "CXX=g++ -m32", while it should use
"CC=/build/prev-gcc/xgcc -m32" "CXX=/build/prev-gcc/xg++ -m32" instead.
However, I'm not sure about the general question behind:
Should it work to bootstrap the multilib-compiler using a non-multilib one?
There's no reason why that should fail as far as the compiler is
concerned. However, there may be other parts of your system that are
not prepared to handle the multilibs.
Jeff