public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/8657: No rule to make target `bootstrap' in directory 'gcc'
Date: Sat, 30 Nov 2002 14:06:00 -0000	[thread overview]
Message-ID: <20021121073601.27366.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/8657; it has been noted by GNATS.

From: Zack Weinberg <zack@codesourcery.com>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: reichelt@igpm.rwth-aachen.de,  gcc-bugs@gcc.gnu.org, 
 gcc-prs@gcc.gnu.org,
	  nobody@gcc.gnu.org,  rolf-alois.walter@db.com,
	  gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/8657: No rule to make target `bootstrap' in directory
 'gcc'
Date: Wed, 20 Nov 2002 23:31:55 -0800

 Neil Booth <neil@daikokuya.co.uk> writes:
 
 > Zack Weinberg wrote:-
 >> In my experience, if objdir is a subdirectory of srcdir AND configure
 >> is invoked by a relative pathname, it doesn't work.
 >
 > For nearly 3 years I have used
 >
 > ../configure --enable-languages=whatever --prefix=whatever
 >
 > and it works fine.  I think a '~' in prefix used to always work, but
 > that broke recently in libstdc++.
 
 Are you building Ada?  IIRC that was where the break was.
 
 zw


             reply	other threads:[~2002-11-21  7:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-30 14:06 Zack Weinberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-30 17:56 Andris Pavenis
2002-11-30 11:36 Neil Booth
2002-11-30 10:26 Zack Weinberg
2002-11-30  9:26 Rolf-Alois Walter
2002-11-29  2:27 Zack Weinberg
2002-11-28 16:08 Neil Booth
2002-11-28 14:01 bangerth
2002-11-28 13:36 reichelt
2002-11-28  8:02 rolf-alois.walter

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=20021121073601.27366.qmail@sources.redhat.com \
    --to=zack@codesourcery.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: 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).