QA script error (libc++)

[Fernando Herrero Carrón]

El 24 jun. 2016 4:23 p. m., "Fernando Apesteguía" <
fernando.apesteguia at gmail.com> escribió:
>
> On Fri, Jun 24, 2016 at 10:25 AM, Fernando Herrero Carrón
> <elferdo at gmail.com> wrote:
> >
> > El 24 jun. 2016 8:16 a. m., "Fernando Apesteguía"
> > <fernando.apesteguia at gmail.com> escribió:
> >>
> >> One of my ports is written in C++. It links agains libc++ that is in
> >> base (/usr/src/contrib/libc++). The port still builds fine and works
> >> but the QA scripts show an error complaining about the executable
> >> being linked to libc++ without the library being listed as an actual
> >> dependency and it suggests to add the following line to the Makefile:
> >>
> >> LIB_DEPENDS+=libc++.so:devel/libc++
> >>
> >> Is this strictly necessary? Would something like this be acceptable?:
> >>
> >> .if !exists(/usr/lib/libc++.so)
> >> ...
> >> LIB_DEPENDS+=libc++.so:devel/libc++
> >> ...
> >> .endif
> >>
> >> Note: the port does not compile on FreeBSD < 10.x
> >>
> >> Thanks in advance.
> >
> > Dear Fernando,
> >
> > I would say adding a dependency on libc++ from ports is not necessary.
On a
> > standard system you can pass the compiler an option like -stdlib=libc++
and
> > it works.
> >
> > This library is usually linked against when compiling with c++11 or
newer.
> > Maybe adding the appropriate compiler option [1] would be a better
choice?
>
> I forgot to mention I'm already using this:
>
> USES= compiler:gcc-c++11-lib
>
> But the QA script still complains.
>

I myself program in c++, have plenty of c++ ports installed and don't have
devel/libc++ on my system.

Could it be that a previous port does install devel/libc++ for you, and
this one links against it by chance? Do you already have devel/libc++
installed when compiling this port?