This is the mail archive of the
java-prs@gcc.gnu.org
mailing list for the Java project.
Re: java/2812: Build failure; missing symbols (iconv) in link of jc1
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, gcc at treblig dot org, java-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, tromey at gcc dot gnu dot org
- Subject: Re: java/2812: Build failure; missing symbols (iconv) in link of jc1
- From: tromey at gcc dot gnu dot org
- Date: 7 Jun 2001 22:52:59 -0000
Synopsis: Build failure; missing symbols (iconv) in link of jc1
Responsible-Changed-From-To: unassigned->tromey
Responsible-Changed-By: tromey
Responsible-Changed-When: Thu Jun 7 15:52:58 2001
Responsible-Changed-Why:
I'm handling it.
State-Changed-From-To: open->analyzed
State-Changed-By: tromey
State-Changed-When: Thu Jun 7 15:52:58 2001
State-Changed-Why:
I don't understand how you could see what you are seeing.
In lex.c, the use of iconv() is predicated on `HAVE_ICONV'.
This in turn is defined only if configure detects
`iconv'. It uses a link test to do this. So this means
(to me) that your libc does have iconv().
Maybe your iconv.h redefines iconv() to libiconv()?
That is what the error messages imply. But then wouldn't
this be a bug in your system?
Is your system typical of Alpha Linux systems?
If so then working around this problem might be appropriate.
If you're running an unusual system then I'd prefer we just
leave it.
Tell me what you think and/or discover...
Thanks!
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2812&database=gcc