public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no> To: gcc-gnats@gcc.gnu.org Subject: bootstrap/10267: Wrong build instructions for *-*-solaris2* Date: Sun, 30 Mar 2003 11:46:00 -0000 [thread overview] Message-ID: <E18zZaS-0003hu-00@bombur.uio.no> (raw) >Number: 10267 >Category: bootstrap >Synopsis: Wrong build instructions for *-*-solaris2* >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: doc-bug >Submitter-Id: net >Arrival-Date: Sun Mar 30 10:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Hallvard B Furuseth >Release: 3.2.2 >Organization: University of Oslo >Environment: System: SunOS bombur.uio.no 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-5_10 Architecture: sun4 host: sparc-sun-solaris2.8 build: sparc-sun-solaris2.8 target: sparc-sun-solaris2.8 configured with: ../gcc-3.2.2/configure --enable-languages=c,c++,f77 --prefix=/usit/bombur/hbf --enable-version-specific-runtime-libs --enable-threads >Description: INSTALL/specific.html#*-*-solaris2* says one should set CONFIG_SHELL to /bin/ksh for configure. However, it is also needed during make bootstrap, since it is bootstrap which configures libstdc++-v3. >How-To-Repeat: env CONFIG_SHELL=/bin/ksh ../gcc-3.2.2/configure make -s bootstrap Output: ... loading cache ../config.cache within ltconfig configure: error: libtool configure failed make[1]: *** [configure-target-libstdc++-v3] Error 1 make: *** [bootstrap] Error 2 >Fix: "... set CONFIG_SHELL to /bin/ksh in your environment before running configure and 'make bootstrap'." I also suggest to remove the 'If you encounter this problem' phrase since it takes two hours before one encounters it. Try 'Therefore, we suggest you set CONFIG_SHELL...'. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-30 10:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-30 11:46 Hallvard B Furuseth [this message] 2003-04-01 22:06 gerald 2003-04-05 15:51 gerald
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=E18zZaS-0003hu-00@bombur.uio.no \ --to=h.b.furuseth@usit.uio.no \ --cc=gcc-gnats@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).