public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk> 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 11:36:00 -0000 [thread overview] Message-ID: <20021121065601.14460.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/8657; it has been noted by GNATS. From: Neil Booth <neil@daikokuya.co.uk> To: Zack Weinberg <zack@codesourcery.com> 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: Thu, 21 Nov 2002 06:50:58 +0000 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. But if configure > is invoked by an absolute pathname, objdir can happily be a > subdirectory of srcdir; and if objdir is not a subdirectory of srcdir, > relative paths work fine. > > I don't remember the exact failure mode, but it was clearly a case of > some shell script fragment somewhere getting mixed up about how many > ../ components it needed to put in a pathname. 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++. Neil.
next reply other threads:[~2002-11-21 6:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-30 11:36 Neil Booth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-30 17:56 Andris Pavenis 2002-11-30 14:06 Zack Weinberg 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=20021121065601.14460.qmail@sources.redhat.com \ --to=neil@daikokuya.co.uk \ --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).