public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Segher Boessenkool <segher@kernel.crashing.org>,
	Prashant <prashanthd.first@gmail.com>
Cc: gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: 'posix_spawnp' error in build
Date: Tue, 26 Dec 2023 00:33:40 +0800	[thread overview]
Message-ID: <22078885f012045083b9287a25dac5157e84ece6.camel@xry111.site> (raw)
In-Reply-To: <20231225162814.GS19790@gate.crashing.org>

On Mon, 2023-12-25 at 10:28 -0600, Segher Boessenkool wrote:
> Hi!
> 
> On Mon, Dec 25, 2023 at 08:11:23PM +0530, Prashant via Gcc-help wrote:
> >  I'm trying to build the gcc repository. Based on the instructions given on
> > the SummerOfCode - GCC Wiki (gnu.org)
> > <https://gcc.gnu.org/wiki/SummerOfCode#Before_you_apply> and GCC for New
> > Contributors — GCC Contributors Guide 0.1 documentation
> > (gcc-newbies-guide.readthedocs.io)
> > <https://gcc-newbies-guide.readthedocs.io/en/latest/>, I have tried the
> > following commands.
> > 
> > 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.

But then you should use "../configure", not "../gcc/configure".  Running
the configure script of a GCC component (instead of the top-level
configure) directly is completely unsupported.

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2023-12-25 16:33 UTC|newest]

Thread overview: 9+ 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 [this message]
2023-12-25 23:00     ` Segher Boessenkool
2023-12-26 14:04       ` Prashant
2023-12-26 15:49         ` Xi Ruoyao
2023-12-27  4:19           ` Prashant
2023-12-27 13:45             ` Xi Ruoyao
2023-12-25 18:26   ` Prashant

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=22078885f012045083b9287a25dac5157e84ece6.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=prashanthd.first@gmail.com \
    --cc=segher@kernel.crashing.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).