public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tromey@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc@treblig.org,
java-prs@gcc.gnu.org, nobody@gcc.gnu.org, tromey@gcc.gnu.org
Subject: Re: java/2812: Build failure; missing symbols (iconv) in link of jc1
Date: Thu, 07 Jun 2001 15:52:00 -0000 [thread overview]
Message-ID: <20010607225259.17538.qmail@sourceware.cygnus.com> (raw)
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
next reply other threads:[~2001-06-07 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-07 15:52 tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-18 10:02 tromey
2001-06-13 14:46 Tom Tromey
2001-05-13 5:26 gcc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010607225259.17538.qmail@sourceware.cygnus.com \
--to=tromey@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=gcc@treblig.org \
--cc=java-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).