Re: Problem with '-static' in 3.0 release on AIX

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

>>>>> Matt Conway writes:

Matt> I have the GNUPro tools for AIX at the front of my path, as can be seen by 
Matt> the type commands below.  Is this wrong to do while configuring?  I 
Matt> thought I needed to do that (along with the --with-gnu-as 
Matt> --with-as=/opt/gnupro/aix43-000718/H-powerpc-ibm-aix4.3.3.0/bin/as) to get 
Matt> gcc to build on AIX.
Matt> y
Matt> Do I need to specify any --enable-threads to get the compiler to work with 
Matt> threaded code, or is this the default with AIX?  If I don't specify 
Matt> pthreads in this way, will the compiler work with code I have that uses 
Matt> pthreads?

Matt> What flags do you use to configure gcc for a bootstrap build?  I can 
Matt> reconfigure/rebuild with those flags and see if my problem goes away.

	Personally, I strongly recommend against using the GNUPro
toolchain or the FSF releases of GAS and GLD to configure and build GCC
3.0.  The GNUPro linker for AIX still has some significant
incompatibilities, partially because the semantics used by the AIX linker
are not well documented.  I also recently have found problems with the
line number debugging information that GAS assembles.

	GCC will configure and build powerpc, power, pthread, and 64-bit
multilibs by default, as well as use shared libraries.  Compile and link
the application with "-pthread" option (not the old -mthreads option).

	I configure and build the compiler with the AIX assembler, linker,
archiver, etc.  Configuring with the GNU assembler causes the
configuration process to find GAS extensions and use them, creating a
dependency on only using that assembler.

	I explicitly create a link from .../build/gcc/as to the GNU
Assembler when I build libstdc++-v3.  I do not use "make bootstrap".  GCC
will use "as" in the -Bxxx/ directory if it finds an executable.

	I only use GAS to compile libstdc++-v3 because those are the only
files with symbol names that cause problems for AIX as.  In fact the only
problem is a few files in libstdc++-v3/src.

David