Ports and WITH_LIBCPLUSPLUS
Dimitry Andric
dim at FreeBSD.org
Sun Feb 3 14:25:49 UTC 2013
On 2013-02-03 14:56, Andreas Nilsson wrote:
> On Sun, Feb 3, 2013 at 2:28 PM, Dimitry Andric <dim at freebsd.org> wrote:
...
>> This is as yet an unsolved problem, as LDFLAGS is the same for both C
>> and C++ link jobs. I think the easiest way would be to set your CXX
>> variable to:
>>
>> CXX=cc -stdlib=libc++
>>
> Wouldn't CXX=CC -stdlib=libc++ be more appropriate, as cc is for c and CC
> for c++, or have that convention gone away?
Sorry, I should have taken one more cup of coffee. :-) 'CC' is not
really recommended anymore, just use:
CXX=c++ -stdlib=libc++
> My adding them to LDFLAGS comes from
> https://wiki.freebsd.org/NewC++Stackwhere it says "Add -stdlib=libc++
> to your compile and link flags..."
Yes, that advice is just fine, but in some cases you cannot influence
the link flags used only for C++ linking. In those cases, you will have
to trick the build system into doing so.
In most cases (but probably not all), this can be done by adding the
required flags to ${CXX}.
> It
> actually made a bunch of the qt4- packages build, they wouldn't without it.
>
> I guess a wiki page tracking the failing packages would be good, but I
> couldn't get the hang of creating a page there :(
This would better be done by a normal exp-run procedure, but those are
offline for the time being.
More information about the freebsd-stable
mailing list