public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> To: danglin@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/7169: /usr/ccs/bin/ld: Unsatisfied symbols: libiconv, li Date: Tue, 02 Jul 2002 16:06:00 -0000 [thread overview] Message-ID: <20020702230601.19352.qmail@sources.redhat.com> (raw) The following reply was made to PR java/7169; it has been noted by GNATS. From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> To: tromey@redhat.com Cc: dave.anglin@nrc.ca, gcc-gnats@gcc.gnu.org, bruno@clisp.org Subject: Re: java/7169: /usr/ccs/bin/ld: Unsatisfied symbols: libiconv, li Date: Tue, 2 Jul 2002 18:58:14 -0400 (EDT) > Maybe the problem here is simply a lack of documentation on telling > configure about libiconv? I could write a doc patch...? You can use > --with-libiconv-prefix=/prefix to tell configure where to find libiconv. > Does doing this cure the problem? Summary: 1) The GNU and HP versions of iconv.h are incompatible. If the GNU version is visible to gcc, then using --with-libiconv-prefix=/prefix where /prefix is the prefix of GNU libiconv works when building with cc. However, libiconv is not used for the build because the GNU header is incompatible with the traditional compiler being used. There could be a small update to the documentation for the --with-libiconv-prefix option. However, I'm going to close the PR since most users will not encounter this problem. 2) Fastjar doesn't build when starting with the HP bundled compiler. Since this uses the stage1 compiler, could building fastjar be disabled if the stage1 compiler doesn't define __STDC__? Another way could be a --disable-fastjar option. Dave -- J. David Anglin dave.anglin@nrc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next reply other threads:[~2002-07-02 23:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-02 16:06 John David Anglin [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-07-03 6:36 Bruno Haible 2002-07-03 6:36 Bruno Haible 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=20020702230601.19352.qmail@sources.redhat.com \ --to=dave@hiauly1.hia.nrc.ca \ --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).