Re: [PATCH] top-level for libvtv: use normal (not raw_cxx) target exports

2015-06-30 Thread Michael Haubenwallner
On 06/30/2015 02:54 PM, Jonathan Wakely wrote: > On 29/06/15 18:57 +0200, Michael Haubenwallner wrote: >> Actually, an unexpected libstdc++-v3/configure change is introduced by some >> inconsistency in >> https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=223196 >> where acinclude.m4 contains

Re: [PATCH] top-level for libvtv: use normal (not raw_cxx) target exports

2015-06-30 Thread Jonathan Wakely
On 29/06/15 18:57 +0200, Michael Haubenwallner wrote: Actually, an unexpected libstdc++-v3/configure change is introduced by some inconsistency in https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=223196 where acinclude.m4 contains different code than the recreated configure: acinclude.m4-3

Re: [PATCH] top-level for libvtv: use normal (not raw_cxx) target exports

2015-06-29 Thread Michael Haubenwallner
On 06/25/2015 09:15 PM, Jeff Law wrote: > 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 t

Re: [PATCH] top-level for libvtv: use normal (not raw_cxx) target exports

2015-06-25 Thread Jeff Law
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 r

Re: [PATCH] top-level for libvtv: use normal (not raw_cxx) target exports

2015-06-22 Thread Michael Haubenwallner
On 06/19/2015 11:36 AM, Paolo Bonzini wrote: > On 09/06/2015 16:22, 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. >> >> The situation to expose the problem

Re: [PATCH] top-level for libvtv: use normal (not raw_cxx) target exports

2015-06-19 Thread Paolo Bonzini
On 09/06/2015 16:22, 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. > > The situation to expose the problem is: > * Use a multilib-enabled x86_64-linux box. >

[PATCH] top-level for libvtv: use normal (not raw_cxx) target exports

2015-06-09 Thread Michael Haubenwallner
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. 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