public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "warrend at mdhost dot cse dot tek dot com" <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 00:20:00 -0000 [thread overview] Message-ID: <20031120002001.18206.qmail@sources.redhat.com> (raw) In-Reply-To: <20030507051600.10657.warren.dodge@tek.com> ------- Additional Comments From warrend at mdhost dot cse dot tek dot com 2003-11-20 00:19 ------- Subject: Re: [3.3 regression] java section can not find libiconv My goal in life is to never set LD_LIBRARY_PATH. I have anyone of hundreds of people who may use what I build. I would like only to say run /path/bin/gcc rather then set some number of environment variables which may break other things that they are doing. I have had a terrible time in getting bootstrapped on Solaris 2.5.1 and Solaris 8. I have no access as ROOT or to /usr/local on these systems. It sure would be useful if someone could write up a procedure on how to 1. start with a downloaded precompiled binary or Sun's compiler. 2. Build a gcc/binutils/libiconv/gettext that resides somewhere other then /usr/local, find the libraries mentioned in step3, and require no special environment variables to be set. This combination is interesting since there is dependancies in multiple directions. 3. Build other library modules (ncurses,zlib,db, etc) and install them in a central location that gcc knows about. I would rather do this then put stuff into gcc's tree to prevent breaking it accidently. The instructions in the installation notes seem only to work properly if there is a system of gnu software installed already. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10657
next prev parent reply other threads:[~2003-11-20 0:20 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 [this message] 2003-11-20 0:31 ` pinskia at gcc dot gnu dot org 2003-11-20 3:29 ` jsturm at gcc dot gnu dot org 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=20031120002001.18206.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).