Re: V3 vs. AIX

[David Edelsohn <dje at watson dot ibm dot com>]

	This reply helped me find part of our earlier discussion.  My
question is not whether libtool has an option to select this behavior, but
what should be the default.  From our earlier discussion:

David>       Also, I really wonder whether ${allow_undefined_flag} should be
David> removed from the non-rtl case.

Alex> Only if a flag is no longer required to create ``incomplete''
Alex> libraries (i.e., libraries with undefined symbols, that should be
Alex> supplied by whoever gets linked with them).

Alex> Note that allow_undefined_flag is set to $no_undefined_flag in case
Alex> -no-undefined is given in the command line, so, even if a flag is no
Alex> longer needed to support incomplete libraries, it's still reasonable
Alex> to keep it in archive_cmds, and set no_undefined_flag to the
Alex> appropriate switch, in case users want to use -no-undefined to make
Alex> sure libraries they create aren't incomplete.

	I think the main point is that libtool adopts the behavior that
most GNU/Linux developers expect: undefined symbols are okay at link-edit
time.  Regardless of whether libtool is using AIX's SysV mode or the
traditional AIX shared library mode, it needs to follow that assumption.
If V3 wants to link with -no-undefined, that would help track down these
problems, but the current philosophy is the programmer needs to request
that pedantic behavior explicitly.

David