Re: java/7169: /usr/ccs/bin/ld: Unsatisfied symbols: libiconv, li

[Bruno Haible <bruno@clisp.org>]

The following reply was made to PR java/7169; it has been noted by GNATS.

From: Bruno Haible <bruno@clisp.org>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: tromey@redhat.com, dave.anglin@nrc.ca, gcc-gnats@gcc.gnu.org
Subject: Re: java/7169: /usr/ccs/bin/ld: Unsatisfied symbols: libiconv, li
Date: Wed, 3 Jul 2002 15:34:17 +0200 (CEST)

 John David Anglin writes:
 > > That's a different thing; you built and installed libiconv with an
 > > ANSI C compiler, and now you go back to a non-ANSI C compiler. Why
 > > don't you use "cc -Ae" instead of "cc" to bootstrap gcc? Why doesn't
 > > gcc by itself add the "-Ae" when it sees an HP-UX compiler?
 > 
 > The "-Ae" option requires purchase of the optional HP ANSI C
 > compiler.
 
 I see.
 
 > Are you saying, that if I build libiconv with a traditional
 > compiler, it will install a header file that is compatible with a
 > traditional compiler?
 
 No, I am saying that libiconv is only buildable with an ANSI C
 compiler, and its installed header file works only with an ANSI C or
 C++ compiler.
 
 So if you insist on using a K&R C compiler, you have to hide
 libiconv's installed file from it - either by doing "make uninstall"
 in libiconv's builddir, or by choosing a different --prefix for gcc.
 
 > If this were fixed, then ...
 
 I won't "fix" this. ANSI C is the standard now. Until you have an ANSI
 C compiler, I'd recommend to not install libiconv. Then, when you have
 bootstrapped gcc once, you can install libiconv, gettext and then
 rebuild gcc with --enable-nls.
 
 Bruno