From: David Edelsohn <dje@watson.ibm.com>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: gcc@gcc.gnu.org
Subject: Re: Top-level Makefile
Date: Fri, 30 Nov 2001 19:33:00 -0000 [thread overview]
Message-ID: <200112010332.WAA23872@makai.watson.ibm.com> (raw)
Message-ID: <20011130193300.yqjdcM6lPuX9OKEQSR2Ey6NqFzwZbR6uFDA7iRfd-6U@z> (raw)
In-Reply-To: <10112010139.AA28635@vlsi1.ultra.nyu.edu>
>>>>> Richard Kenner writes:
> Note that I use
> $ make SHELL=/usr/local/bin/bash CONFIG_SHELL=/usr/local/bin/bash ... bootstrap
> Setting the appropriate environment variables should be equivalent with
> GNU Make, but I am not sure.
Richard> You lost me. I was doing configure, not make.
As others have mentioned, "configure" is run at different times.
The first manual configure is for the build of the compiler itself. Then
"make bootstrap" or "make all" in the top-level runs configure implicitly
to set up the target libraries based on the target compiler just built.
libstdc++-v3 is one of those directories in which "configure" is run by
Make.
The upshot is that you need to specify the shell to Make so that
it is used by the libstdc++-v3 configure.
David
next prev parent reply other threads:[~2001-11-30 19:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 14:25 Richard Kenner
2001-11-24 15:02 ` Zack Weinberg
2001-11-30 18:14 ` Zack Weinberg
2001-11-24 16:57 ` Bryce McKinlay
2001-11-30 18:32 ` Bryce McKinlay
2001-11-24 18:09 ` David Edelsohn [this message]
2001-11-30 19:33 ` David Edelsohn
2001-11-30 17:44 ` Richard Kenner
-- strict thread matches above, loose matches on Subject: below --
2001-11-24 18:04 Richard Kenner
2001-11-24 19:19 ` Zack Weinberg
2001-11-30 20:16 ` Zack Weinberg
2001-11-30 19:01 ` Richard Kenner
2001-11-22 20:31 Richard Kenner
2001-11-23 2:01 ` David Edelsohn
2001-11-30 8:17 ` David Edelsohn
2001-11-30 3:43 ` Richard Kenner
2001-11-22 20:28 Richard Kenner
2001-11-24 16:41 ` Zack Weinberg
2001-11-30 18:17 ` Zack Weinberg
2001-11-30 3:05 ` Richard Kenner
2001-11-21 14:38 Richard Kenner
2001-11-21 15:14 ` Alexandre Oliva
2001-11-29 8:01 ` Alexandre Oliva
2001-11-21 15:16 ` David Edelsohn
2001-11-21 15:52 ` Phil Edwards
2001-11-21 19:20 ` David Edelsohn
2001-11-21 22:04 ` Phil Edwards
2001-11-29 11:04 ` Phil Edwards
2001-11-29 10:27 ` David Edelsohn
2001-11-29 8:55 ` Phil Edwards
2001-11-29 8:09 ` David Edelsohn
2001-11-29 6:50 ` Richard Kenner
2001-11-21 14:00 Richard Kenner
2001-11-21 14:27 ` Alexandre Oliva
2001-11-29 6:46 ` Alexandre Oliva
2001-11-21 15:59 ` Zack Weinberg
2001-11-29 9:11 ` Zack Weinberg
2001-11-22 13:53 ` Geoff Keating
2001-11-30 0:08 ` Geoff Keating
2001-11-29 5:58 ` Richard Kenner
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=200112010332.WAA23872@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).