From: Segher Boessenkool <segher@kernel.crashing.org>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Prashant <prashanthd.first@gmail.com>,
gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: 'posix_spawnp' error in build
Date: Mon, 25 Dec 2023 17:00:33 -0600 [thread overview]
Message-ID: <20231225230033.GT19790@gate.crashing.org> (raw)
In-Reply-To: <22078885f012045083b9287a25dac5157e84ece6.camel@xry111.site>
On Tue, Dec 26, 2023 at 12:33:40AM +0800, Xi Ruoyao wrote:
> On Mon, 2023-12-25 at 10:28 -0600, Segher Boessenkool wrote:
> > > 1) git clone git://gcc.gnu.org/git/gcc.git
> > > 2) cd gcc & ./contrib/download_prerequisites
> > > 3) mkdir objdir & cd objdir
> > > 4) ../gcc/configure --prefix=/home/path/to/gcc --enable-languages=c,c++
> >
> > That is wrong. Build dir as a subdir of the source dir is not
> > supported. It might work in many cases, but that does not mean it is
> > okay to do.
>
> It *is* supported, per discussion at
> https://gcc.gnu.org/pipermail/gcc-patches/2023-November/638760.html.
Huh, okay. That changed "recently" then, for some elongated timescale
anyway :-)
> But then you should use "../configure", not "../gcc/configure".
Ha! I didn't even notice that.
> Running
> the configure script of a GCC component (instead of the top-level
> configure) directly is completely unsupported.
Without all the necessary configuration arguments, yeah. So it is still
easier to just make an actually separate object dir -- even if only so
you can just blow it away when you want to start over :-)
Segher
next prev parent reply other threads:[~2023-12-25 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-25 14:41 Prashant
2023-12-25 16:28 ` Segher Boessenkool
2023-12-25 16:33 ` Xi Ruoyao
2023-12-25 23:00 ` Segher Boessenkool [this message]
2023-12-26 14:04 ` Prashant
2023-12-25 18:26 ` Prashant
2023-12-29 22:40 ` Dave Blanchard
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=20231225230033.GT19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=prashanthd.first@gmail.com \
--cc=xry111@xry111.site \
/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).