public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gcc@treblig.org
To: gcc-gnats@gcc.gnu.org
Subject: java/2812: Build failure; missing symbols (iconv) in link of jc1
Date: Sun, 13 May 2001 05:26:00 -0000	[thread overview]
Message-ID: <20010513122505.28452.qmail@sourceware.cygnus.com> (raw)

>Number:         2812
>Category:       java
>Synopsis:       Build failure; missing symbols (iconv) in link of jc1
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun May 13 05:26:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Dave Gilbert
>Release:        current Gcc 3 branch cvs (as of 12 May 2001)
>Organization:
>Environment:
Linux/Alpha, libc 2.1.2
>Description:
When doing a make bootstrap on my Linux/Alpha installation the
jc1 build fails with a number of missing symbols from the iconv library
(see below).  I think the issue might be that older libc's don't have
iconv in, but have an external iconv library.

stage1/xgcc -Bstage1/ -B/home/dg/egcs/alphaev56-unknown-linux-gnu/bin/  -DIN_GCC    -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H  -o jc1 java/parse.o java/class.o java/decl.o java/expr.o java/constants.o java/lang.o java/typeck.o java/except.o java/verify.o java/zextract.o java/jcf-io.o java/jcf-parse.o java/mangle.o java/mangle_name.o java/jcf-write.o java/buffer.o java/check-init.o java/jcf-depend.o java/jcf-path.o java/xref.o java/boehm.o mkdeps.o toplev.o libbackend.a -L../zlib -lz obstack.o         ../libiberty/libiberty.a
java/parse.o: In function `java_new_lexer':
java/parse.o(.text+0x7c0): undefined reference to `libiconv_open'
java/parse.o(.text+0x7c4): undefined reference to `libiconv_open'
java/parse.o(.text+0x8a0): undefined reference to `libiconv_open'
java/parse.o(.text+0x8a4): undefined reference to `libiconv_open'
java/parse.o(.text+0x90c): undefined reference to `libiconv'
java/parse.o(.text+0x910): undefined reference to `libiconv'
java/parse.o(.text+0x92c): undefined reference to `libiconv_close'
java/parse.o(.text+0x930): undefined reference to `libiconv_close'
java/parse.o: In function `java_destroy_lexer':
java/parse.o(.text+0xa24): undefined reference to `libiconv_close'
java/parse.o(.text+0xa28): undefined reference to `libiconv_close'
java/parse.o: In function `java_read_char':
java/parse.o(.text+0xd10): undefined reference to `libiconv'
java/parse.o(.text+0xd14): undefined reference to `libiconv'
collect2: ld returned 1 exit status
>How-To-Repeat:

>Fix:
I added -liconv to the link line and it built.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-05-13  5:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-13  5:26 gcc [this message]
2001-06-07 15:52 tromey
2001-06-13 14:46 Tom Tromey
2001-07-18 10:02 tromey

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=20010513122505.28452.qmail@sourceware.cygnus.com \
    --to=gcc@treblig.org \
    --cc=gcc-gnats@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).