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: Fri, 7 Dec 2001 11:10:51 -0800

 Tom,
 
 I've tried an experiment by invoking each configure using the --help option
 and redirecting to a file. I edited the file and specified parameters that
 I wanted for each and then copied all  the parameters into one file
 (script), deleted the dups and tried to build gcc. I don't think it worked
 but can't remember. Does this sound like what you had in mind? I'll try to
 do the build again and let you know...
 
 Regards and thanks for your time AND help,
 
 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