Total confusion over toolchain/xdev behavior

[Dimitry Andric]

On 08 Jul 2014, at 03:56, Warner Losh <imp at bsdimp.com> wrote:

> 
> On Jul 7, 2014, at 7:29 PM, Warner Losh <imp at bsdimp.com> wrote:
>> 
>> About the rest… Yea, you may be right….  MK_GNUCXX is an odd duck, and that’s
>> likely the problem that should be fixed in a different way. It is really an internal
>> variable that should be set based on the actual compiler type (possibly with an
>> override for the odd-duck pair of clang and libstdc++ which may not be worth
>> supporting). It is telling us we’re doing something horribly wrong and we should listen
>> to that rather than add another compiler-related kludge to the build system.  I’ll work
>> on that bit.
> 
> Perhaps
> 	http://people.freesbd.org/~imp/patch-queue/86gnucxx
> might be the best way to cope…
> 
> Comments?

This would make it impossible to build libstdc++ with clang, and why remove MK_GNUCXX at all[1]?  Maybe the option should be renamed to MK_LIBSTDCXX or MK_LIBSTDCPLUSPLUS, since that is basically what it does: enable or disable building libstdc++ and its dependent components.

If the compiler is base gcc, you *must* build libstdc++, since it cannot build libc++.  But if you are using e.g. gcc 4.8 as an external toolchain, you could just as easily disable libstdc++, and build libc++ instead.  I think both should be a user-selectable option.

-Dimitry

[1]: That is, unless somebody is planning on removing libstdc++ altogether... but then g++ will also have to go. ;)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20140708/88a0ec22/attachment.sig>