Date: Mon, 1 Mar 2004 12:22:11 +0300 From: Andrey Chernov <ache@nagual.pp.ru> To: John Birrell <jb@cimlogic.com.au> Cc: current@freebsd.org Subject: Re: Assembler broken by getopt_long_only changes Message-ID: <20040301092211.GA9093@nagual.pp.ru> In-Reply-To: <20040301192548.M16237@freebsd3.cimlogic.com.au> References: <20040301192548.M16237@freebsd3.cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> ports/graphics/tiff runs configure without using the -pipe argument to gcc.
> The new behaviour of getopt_long_only() returns -1 when it encounters an
> argument which isn't an option. The old behaviour (confirmed by winding
> the current machine back to Feb 20, 2004 sources) returns 1. The change
> causes 'as' to ignore a file name argument and hang waiting on a read from
> stdin. Most people won't see the problem because they use the -pipe argument
> to gcc which passes '-' instead of the file name.
The bug is somewhere deeper, than your analysis, because all the same
commands (cc, as) called by hand with the same args works, they not works
only from tiff's configure. Maybe configure do something with
environment... I'll look into this ASAP.
If it is {Open,Net}BSD getopt_long* bug, it should be fixed there in
anycase, because other ports configures likes to find getopt_long* in libc
first.
--
Andrey Chernov | http://ache.pp.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040301092211.GA9093>