public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Prashant <prashanthd.first@gmail.com>
Cc: gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: 'posix_spawnp' error in build
Date: Mon, 25 Dec 2023 10:28:14 -0600	[thread overview]
Message-ID: <20231225162814.GS19790@gate.crashing.org> (raw)
In-Reply-To: <CAEW0Brr85gj=yHyYnb+OFWsnHSohf0YmdNBN7kObg8zQVwjp9w@mail.gmail.com>

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.

> Running the 5th throws the following error:
> 'xgcc: fatal error: cannot execute ‘cc1plus’: posix_spawnp: No such file or
> directory
> compilation terminated.'

I don't know if that is one of the weird problems caused by this.  Easy
enough to find out.  First "make distclean", and then "git status".

The error message says that the newly compiled compiler driver ("xgcc",
which will be insbtalled as just "gcc" eventually) cannot execute the
newly compiled actual C++ compiler ("cc1plus"), not from the place it
thinks it put it, anyway.

gl;hf, happy holidays, let us know how it went / what else you find out,


Segher

  reply	other threads:[~2023-12-25 16:29 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 [this message]
2023-12-25 16:33   ` Xi Ruoyao
2023-12-25 23:00     ` Segher Boessenkool
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=20231225162814.GS19790@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=prashanthd.first@gmail.com \
    /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).