public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Sturm <jsturm@one-point.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/10657: java section can not find ;ibiconv
Date: Wed, 07 May 2003 22:56:00 -0000	[thread overview]
Message-ID: <20030507225600.28252.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/10657; it has been noted by GNATS.

From: Jeff Sturm <jsturm@one-point.com>
To: gcc-gnats@gcc.gnu.org, <gcc-bugs@gcc.gnu.org>, <mark@codesourcery.com>,
   <warren.dodge@tek.com>
Cc:  
Subject: Re: bootstrap/10657: java section can not find ;ibiconv
Date: Wed, 7 May 2003 18:53:02 -0400 (EDT)

 In the root of your failing build tree, can you run
 
 grep iconv config.cache
 
 and paste the output?  In particular, I'm interested in am_cv_func_iconv,
 am_cv_lib_iconv and am_cv_lib_iconv_ldpath.
 
 I could not reproduce this problem on my Solaris 8 machine yet.  Moreover,
 Solaris 8 does not have a separate libiconv, it is integrated with libc.
 
 I'm guessing your problem may occur if all the following are true:
 
 a) Your bootstrap compiler is GCC and lives in a different --prefix than
 that you are configuring for
 b) GNU libiconv is installed in the same prefix as your bootstrap compiler
 c) libiconv is not available in /usr/lib or one of the system search paths
 
 Jeff
 


             reply	other threads:[~2003-05-07 22:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 22:56 Jeff Sturm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 13:58 jsturm
2003-05-08 10:06 Christian Ehrhardt
2003-05-07 13:56 Christian Ehrhardt
2003-05-07  5:16 warren.dodge

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=20030507225600.28252.qmail@sources.redhat.com \
    --to=jsturm@one-point.com \
    --cc=gcc-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).