public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/10811: libjava/libltdl/configure fails Date: Sat, 17 May 2003 09:06:00 -0000 [thread overview] Message-ID: <20030517090600.11546.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/10811; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@yahoo.com> To: Ari Pollak <ari@ccs.neu.edu>, gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/10811: libjava/libltdl/configure fails Date: Sat, 17 May 2003 01:54:50 -0700 (PDT) --- Ari Pollak <ari@ccs.neu.edu> wrote: > Yes, either make bootstrapping or making with > CONFIG_SHELL set to ksh > makes it run fine. What exactly is the difference in > the end result > between 'make' and 'make bootstrap'? Make bootstrap builds the compiler in 3 stages. stage 1: build compiler with existing compiler. stage 2: build compiler with stage 1 compiler stage 3: build compiler with stage 1 compiler (again) final stage: compare the files created in stage 2 and 3, they must be identical! make just does stage 1. theoretically, if make bootstrap works, make should work. But the /bin/sh issues are simply bugs in the Solaris shell, which seem to trigger more or less randomly. CONFIG_SHELL=/bin/ksh is supposed to fix this by providing a reliable shell. Dara P.S. That doesn't mean that it wouldn't be nice to get everything to work with /bin/sh, simply that doing so is difficult, and no one's yet succeeded. __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
next reply other threads:[~2003-05-17 9:06 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-17 9:06 Dara Hazeghi [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-21 8:43 ebotcazou 2003-05-17 4:16 Ari Pollak 2003-05-17 1:56 Dara Hazeghi 2003-05-17 1:16 Ari Pollak 2003-05-17 0:36 Dara Hazeghi 2003-05-16 17:16 Ari Pollak 2003-05-16 7:26 ebotcazou 2003-05-16 4:16 ari
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=20030517090600.11546.qmail@sources.redhat.com \ --to=dhazeghi@yahoo.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: 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).