public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org> To: danglin@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/7169: /usr/ccs/bin/ld: Unsatisfied symbols: libiconv, li Date: Wed, 03 Jul 2002 06:36:00 -0000 [thread overview] Message-ID: <20020703133603.8750.qmail@sources.redhat.com> (raw) The following reply was made to PR java/7169; it has been noted by GNATS. From: Bruno Haible <bruno@clisp.org> To: "John David Anglin" <dave@hiauly1.hia.nrc.ca> Cc: tromey@redhat.com, dave.anglin@nrc.ca, gcc-gnats@gcc.gnu.org Subject: Re: java/7169: /usr/ccs/bin/ld: Unsatisfied symbols: libiconv, li Date: Wed, 3 Jul 2002 15:35:44 +0200 (CEST) John David Anglin writes: > > libiconv installs its header in $prefix/include and its library in > > $prefix/lib. If gcc now looks in one of these directories but not the > > other, you get the link error that you saw. > > If I add "-liconv" to the link command for jc1, the link is successful. Good. That excludes my prior hypothesis. > The reason that there isn't a library specification in the command is > that the HP iconv routines are in libc and those were the ones found > by configure. Which means that the aclocal.m4 macros are outdated and ought to be upgraded to gettext 0.11.2. Bruno
next reply other threads:[~2002-07-03 13:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-03 6:36 Bruno Haible [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-07-03 6:36 Bruno Haible 2002-07-02 16:06 John David Anglin 2002-07-02 14:26 John David Anglin 2002-07-02 13:56 John David Anglin 2002-07-02 12:56 Bruno Haible 2002-07-02 12:16 John David Anglin 2002-07-02 12:07 John David Anglin
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=20020703133603.8750.qmail@sources.redhat.com \ --to=bruno@clisp.org \ --cc=danglin@gcc.gnu.org \ --cc=gcc-prs@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: linkBe 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).