java/4972: undefined reference to libiconv

[George.R.Goffe@seagate.com]

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

From: George.R.Goffe@seagate.com
To: tromey@redhat.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/4972: undefined reference to libiconv
Date: Sat, 8 Dec 2001 12:41:18 -0800

 Tom,
 
 Your solution worked!!!! You're a genius!!!!
 
 There's another problem which has appeared since we're past the libiconv
 problem.
 
 The configure process in the configure-target-libiberty part claims that
 the C compiler can not create executibles. I'm not sure which config.log
 illustrates the error so I've gathered the build log, install log (make
 install), and ALL the config.logs. I've seen this problem before but
 thought it was just something I did wrong because I was trying to hack past
 the libiconv  problem. I seem to recall seeing a -m64 option which is a
 request to generate 64bit code I think. The system is a ultra 5 with 64bit
 enabled. Should I report this as a "new" bug?
 
 Thanks A LOT for all your help!!!!!
 
 If you need me to try things in the future just let me know, I'll do the
 best I can. (This applies to all the other developers too).
 
 Regards,
 
 George...
 
 
 
 
 
 
 Tom Tromey <tromey@redhat.com> on 12/07/2001 11:02:14 AM
 
 Please respond to tromey@redhat.com
 
 To:   George.R.Goffe@seagate.com
 cc:   gcc-gnats@gcc.gnu.org
 
 Subject:  Re: java/4972: undefined reference to libiconv
 
 
 >>>>> "George" == George R Goffe <George.R.Goffe@seagate.com> writes:
 
 Hi.  Please keep gcc-gnats on the CC line so that we can track your
 responses.  Thanks.
 
 George> How does one pass parameters to the other configures?
 
 If you pass an option to the top-level configure it will be passed
 automatically to the other ones.
 
 George> Is there a document describing how this is done? Can you point
 George> me to where it is?
 
 I don't know if there is one or not :-(
 
 George> p.s., The config.log I sent you was from last weeks
 George> snapshot. Do you still need the build log as well?
 
 Nope.
 
 
 Could you try a build using --with-libiconv-prefix=FOO and tell me if
 that solves your problem?  If so I'm going to send a bug report to
 Bruno Haible (he wrote the autoconf code that deals with libiconv) and
 then close this PR.
 
 Thanks,
 Tom