"Rafael Rivera Jr." <[EMAIL PROTECTED]> writes:
> Correct me if I'm wrong, but doesn't autoconf read in the
> configure.ac and spit out the configure script?
Yes, but it also reads other files.
> The configure.ac for the gettext package has no references to this
> code.
But other files do, and
Hi Rafael,
* Rivera, R wrote on Sun, Feb 26, 2006 at 08:38:34PM CET:
>
> New to this list. It seems the logic behind determining whether or not libc
> should be explicitly linked is backwards (in a generated configure script).
This is a Libtool question, and as such would've fit better on one of
"Rivera, R" <[EMAIL PROTECTED]> writes:
> (eval $archive_cmds 2\>\&1 \| grep \" -lc \" \>/dev/null 2\>\&1) 2>&5
That doesn't appear to be Autoconf code; most likely it was in some of
the macros or the configure.ac file of the package you're looking at,
and Autoconf simply copied the code into "co
Ralf,
Thanks for the libtool pointer. I have CCed the proper list but intend
on removing autoconf@gnu.org in future replies.
On SkyOS (and cross-compiling tools for SkyOS on Cygwin), libsky gets
implicitly linked but because we failed this check, -lc is getting added
( archive_cmds_need_lc=y
