Date: Thu, 23 Jan 2014 12:36:43 -0800 From: Yuri <yuri@rawbw.com> To: marino@freebsd.org, =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@bluelife.at> Cc: ports@freebsd.org, Gerald Pfeifer <gerald@pfeifer.com>, Shane Ambler <FreeBSD@shaneware.biz> Subject: Re: USE_GCC doesn't set rpath Message-ID: <52E17D5B.1050003@rawbw.com> In-Reply-To: <52E173E4.2050003@marino.st> References: <52DEE7EE.6010909@rawbw.com> <52DF0346.6000108@ShaneWare.Biz> <52E167BF.8050103@rawbw.com> <CAE-m3X0cMxJ_mpPZ_AoDb17G9Dg4F_Sj45KsZi-hYnd9mguhLw@mail.gmail.com> <52E173E4.2050003@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/23/2014 11:56, John Marino wrote: > While I basically agree with this sentiment, is not it just ports that > use C++ that are affected? Could not this be narrowed down to "We need > a single compiler for ports that use C++" ? It's not necessarily just C++. Python ports bound to C++ libraries with USE_GCC would create even more grave problem. It will be needed to create a special version of python with this rpath in it. And if there is a mix of different versions of gcc in various dependencies it would be just impossible to run such program due to conflicts. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52E17D5B.1050003>