Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Feb 2021 12:51:27 +0100
From:      Jan Beich <jbeich@FreeBSD.org>
To:        Olivier Certner <olivier.freebsd@free.fr>
Cc:        Kurt Jaeger <pi@freebsd.org>, Gerald Pfeifer <gerald@pfeifer.com>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   Re: svn commit: r565330 - in head: . www www/palemoon www/palemoon/files
Message-ID:  <czws-fhhc-wny@FreeBSD.org>
In-Reply-To: <6023468.TRTBLuF5rb@ravel> (Olivier Certner's message of "Mon, 22 Feb 2021 11:30:13 %2B0100")
References:  <202102151919.11FJJMGp064158@repo.freebsd.org> <7595c273-707c-85f-4241-4ed264a257b9@pfeifer.com> <6023468.TRTBLuF5rb@ravel>

next in thread | previous in thread | raw e-mail | index | archive | help
Olivier Certner <olivier.freebsd@free.fr> writes:

> I think it would be great if the ports infrastructure allowed to specify 
> building with GCC, but using libc++'s headers and linking against it,

Did you try USES=compiler:gcc-c++11-lib ?

https://svnweb.freebsd.org/changeset/ports/350623
https://svnweb.freebsd.org/changeset/ports/428641

> removing '-rpath', which is not necessary for a build-only dependency (I 
> wonder if it is still necessary at all for runtime dependencies; might be for 
> architectures that have not switched to clang; -rpath should be eliminated at 
> most costs, but this is another discussion).

https://wiki.freebsd.org/libgcc%20problem probably still affects
USES=fortran consumers.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?czws-fhhc-wny>