public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsturm at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/10657] [3.3 regression] java section can not find libiconv Date: Thu, 20 Nov 2003 03:29:00 -0000 [thread overview] Message-ID: <20031120032941.634.qmail@sources.redhat.com> (raw) In-Reply-To: <20030507051600.10657.warren.dodge@tek.com> ------- Additional Comments From jsturm at gcc dot gnu dot org 2003-11-20 03:29 ------- (In reply to comment #13) > Sorry but you will need to set LD_LIBRARY_PATH unless you add -R to all your compiling of your > programs in the nonstandard path. Andrew, I think there is a valid complaint here, though it will not be fixed for 3.4, and is probably not a regression either. configure is detecting and using libiconv based on the bootstrap compiler's settings. This fails in stage2 when the bootstrap compiler is no longer used. There are workarounds, you mentioned LD_LIBRARY_PATH and -R. Or uninstall libiconv from the bootstrap compiler's path. Or install it first in ${prefix}. Nevertheless it's bogus of configure to do this, and completely preventable when bootstrap moves to toplevel (so stage2 can reconfigure following bootstrap). I think it should be kept open, perhaps at lower priority. Is there a PR you know of for toplevel bootstrap? If so, this one could depend on it. -- What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | Target Milestone|3.4 |3.5 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10657
next prev parent reply other threads:[~2003-11-20 3:29 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20030507051600.10657.warren.dodge@tek.com> 2003-06-08 1:44 ` jsturm@gcc.gnu.org 2003-06-11 22:47 ` pinskia@physics.uc.edu 2003-06-11 23:23 ` warrend@mdhost.cse.tek.com 2003-07-12 3:19 ` neroden at gcc dot gnu dot org 2003-07-13 16:17 ` jsturm at gcc dot gnu dot org 2003-10-24 20:40 ` neroden at gcc dot gnu dot org 2003-10-24 20:41 ` neroden at gcc dot gnu dot org 2003-11-19 23:25 ` pinskia at gcc dot gnu dot org 2003-11-20 0:20 ` warrend at mdhost dot cse dot tek dot com 2003-11-20 0:31 ` pinskia at gcc dot gnu dot org 2003-11-20 3:29 ` jsturm at gcc dot gnu dot org [this message] 2003-11-28 8:40 ` pinskia at gcc dot gnu dot org 2004-01-14 4:45 ` [Bug bootstrap/10657] " pinskia at gcc dot gnu dot org 2004-12-05 17:02 ` [Bug java/10657] " pinskia at gcc dot gnu dot org
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=20031120032941.634.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).