From: Zack Weinberg <zack@codesourcery.com>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: dje@watson.ibm.com, gcc@gcc.gnu.org
Subject: Re: Top-level Makefile
Date: Sat, 24 Nov 2001 15:02:00 -0000 [thread overview]
Message-ID: <20011130181430.B30901@codesourcery.com> (raw)
In-Reply-To: <10112010139.AA28635@vlsi1.ultra.nyu.edu>
On Fri, Nov 30, 2001 at 08:39:00PM -0500, Richard Kenner wrote:
> 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.
>
> You lost me. I was doing configure, not make.
The libstdc++ configure script shouldn't run during initial configure;
it's target-only. It is supposed to be run during the course of the
"make bootstrap" from top level.
Can you post the precise sequence of commands you are using, starting
from an empty build directory?
zw
WARNING: multiple messages have this Message-ID
From: Zack Weinberg <zack@codesourcery.com>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: dje@watson.ibm.com, gcc@gcc.gnu.org
Subject: Re: Top-level Makefile
Date: Fri, 30 Nov 2001 18:14:00 -0000 [thread overview]
Message-ID: <20011130181430.B30901@codesourcery.com> (raw)
Message-ID: <20011130181400.CFQ0IrxJc2HDBBU-gxPfgdhqK5JksxNnNft39lWa1pY@z> (raw)
In-Reply-To: <10112010139.AA28635@vlsi1.ultra.nyu.edu>
On Fri, Nov 30, 2001 at 08:39:00PM -0500, Richard Kenner wrote:
> 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.
>
> You lost me. I was doing configure, not make.
The libstdc++ configure script shouldn't run during initial configure;
it's target-only. It is supposed to be run during the course of the
"make bootstrap" from top level.
Can you post the precise sequence of commands you are using, starting
from an empty build directory?
zw
next prev parent reply other threads:[~2001-12-01 2:14 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 [this message]
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
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=20011130181430.B30901@codesourcery.com \
--to=zack@codesourcery.com \
--cc=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).