RE: Bootstrapping 3.4.2 on AIX 5.1.0.0

["Grubb, Richard L" <richard dot l dot grubb at boeing dot com>]

I looked in the gcc libraries that were built so far during the
bootstrapping phase; gcc/libbackend.a, intl/libintl.a, and
libiberty/libiberty.a using the command:
 nm -g <insert_appropriate_library_name_here>; grep iconv

intl/libintl.a contains the symbols .iconv, .iconv_open and .iconv_close
(just like the AIX library /usr/lib/libintl.a), but not .libiconv,
.libiconv_open or .libiconv_close

So why does the bootstrap build process tack on the "lib" prefix to these
symbols?

I haven't tried configuring with --disable-nls yet. I'll do that soon.

Thanks

-----Original Message-----
From: David Edelsohn [mailto:dje@watson.ibm.com] 
Sent: Wednesday, November 10, 2004 12:35 PM
To: Grubb, Richard L
Cc: gcc-help@gcc.gnu.org
Subject: Re: Bootstrapping 3.4.2 on AIX 5.1.0.0


> ld: 0711-317 ERROR: Undefined symbol: .libiconv
> ld: 0711-317 ERROR: Undefined symbol: .libiconv_open
> ld: 0711-317 ERROR: Undefined symbol: .libiconv_close

	You can find the source of those symbols by looking in the various
libraries (libintl, libiberty, libbackend.

	You might try configuring with --disable-nls to work around the
build problem.

David

Attachment: smime.p7s
Description: S/MIME cryptographic signature