Re: config-ml.in AIX multilibs and documentation

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

>>>>> Alexandre Oliva writes:

Alex> This is indeed ok, but I'm wondering if it would be too hard to
Alex> detect, in case of native builds, whether linking ppc64 and pthread
Alex> libraries is going to work, and automatically disable them if it
Alex> fails, just like it is done on IRIX 6 for the 64-bit ABI.

	If the aix64 multilib could be disabled automatically for V3
configuration, but not all libraries, I would find that much more
palatable.  Disabling all of aix64 because of one component seems wrong.
For instance, if a user does not download and/or does not configure the
G++, there will be no problem.  Should a user not be able to configure and
build the core GCC C compiler 64-bit libgcc.a or G77 because V3 fails?

Alex> At the very least, these configure flags should be documented.  I
Alex> can't find any documentation of --disable-aix64 nor --disable-pthread
Alex> in the documentation directory.  In fact, I can't find anything about
Alex> softfloat either.

	I checked for various config-ml.in flags throughout the
documentation in the entire gcc-3.0 tree.  None are documented.  The
multilib invocation flags are documented in invoke.texi, but disabling
configuration is not mentioned in install.texi.

	install.texi mentions:

--disable-shared
--disable-cpp
--disable-libgcj
--disable-win32-registry
--disable-nls

	None of the target-specific flags are mentioned.

	I can add the AIX documention, but that means creating a new
section in install.texi.  I would suggest doing this as a comprehensive
documentation of all of those options.  I would like to coordinate that
with Jerry for gcc-3.0.1.

David