Date: Sun, 3 Feb 2013 15:33:40 +0100 From: Andreas Nilsson <andrnils@gmail.com> To: Dimitry Andric <dim@freebsd.org> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: Ports and WITH_LIBCPLUSPLUS Message-ID: <CAPS9%2BSujHg8PYKiTvHPx-xxKU_YOpaZ1PmKWOkK5GvHk-BQH8w@mail.gmail.com> In-Reply-To: <510E7365.3060807@FreeBSD.org> References: <CAPS9%2BSsKqM%2B0Zo71LRxTfUPVOBhUaCTqrXDuHv30e76EH7YWCw@mail.gmail.com> <510E65FA.4040900@FreeBSD.org> <CAPS9%2BSv3QTTK50=67F82=9jf4T0%2BGa0EoL_Qzh0og=AhEdsAiQ@mail.gmail.com> <510E7365.3060807@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 3, 2013 at 3:25 PM, Dimitry Andric <dim@freebsd.org> wrote: > On 2013-02-03 14:56, Andreas Nilsson wrote: > >> On Sun, Feb 3, 2013 at 2:28 PM, Dimitry Andric <dim@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++ > Ah, yes. To little coffee here as well. > > My adding them to LDFLAGS comes from >> https://wiki.freebsd.org/NewC+**+Stackwhere<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}. Good point. > > > > 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. > On a side note: I forget the actual logs. They are now available as logs.tgz at same base URL. Best regards Andreas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPS9%2BSujHg8PYKiTvHPx-xxKU_YOpaZ1PmKWOkK5GvHk-BQH8w>