svn commit: r384894 - head/lang/gcc5-aux

[John Marino]

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.

John