Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Apr 2015 20:10:53 +0200
From:      Tijl Coosemans <tijl@FreeBSD.org>
To:        John Marino <freebsd.contact@marino.st>
Cc:        John Marino <marino@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   Re: svn commit: r384894 - head/lang/gcc5-aux
Message-ID:  <20150428201053.0dad1c6c@kalimero.tijl.coosemans.org>
In-Reply-To: <553FC940.8050106@marino.st>
References:  <201504281216.t3SCGYSp044760@svn.freebsd.org> <20150428165407.1bb95495@kalimero.tijl.coosemans.org> <553FA06F.8000602@marino.st> <20150428171258.4668b0ab@kalimero.tijl.coosemans.org> <553FA574.3010503@marino.st> <20150428173654.2baa2951@kalimero.tijl.coosemans.org> <553FAB80.1040300@marino.st> <20150428193838.45a12925@kalimero.tijl.coosemans.org> <553FC940.8050106@marino.st>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 28 Apr 2015 19:54:08 +0200 John Marino <freebsd.contact@marino.st> wrote:
> On 4/28/2015 19:38, Tijl Coosemans wrote:
>> The command that fails on Dragonfly seems exactly the same as on
>> FreeBSD 10.  There's no -L/usr/local/lib there either.  The reason it
>> doesn't fail on FreeBSD is probably because gcc searches /usr/local/lib
>> implicitly (which I always found strange).  Maybe that is not the case
>> on Dragonfly.  Does this command work for instance:
>> 
>> echo 'int main(void) { return 0; }' | gcc5 -x c -o test - -lintl 
> 
> In the general case, I can confirm DragonFly gcc does *not* search
> /usr/local/lib.  The LDFLAGS have to be explicitly set.  Any gcc built
> by ports will search there.  I don't know what the FreeBSD base
> compilers do.
> 
> However, this is a special case.  The compiler used is provided to
> bootstrap (needed for Ada).  It's possible the FreeBSD bootstraps do
> search there and DragonFly bootstraps do not.  This could be explained
> by not patching freebsd spec files from the vendor, so default behavior
> is maintained.
> 
> I'd actually say the chances of this being the case is pretty good.  The
> solution of explicitly specifying LDFLAGS in all cases works though.

Ok, then maybe all that's needed is to add back _configargs (without
LIBS).



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