From: Prashant <prashanthd.first@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: 'posix_spawnp' error in build
Date: Mon, 25 Dec 2023 23:56:30 +0530 [thread overview]
Message-ID: <CAEW0Brq34=dx3DCxixV3WdyChCL_G_q3ABaqtEpTFYw3+paY4A@mail.gmail.com> (raw)
In-Reply-To: <20231225162814.GS19790@gate.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On Mon, 25 Dec 2023 at 22:00, Segher Boessenkool <segher@kernel.crashing.org>
wrote:
> Hi!
>
> > 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.
>
> I'm really sorry to miss out this important piece of information. Before
> the execution of step 3, I'm out of the gcc repo. So 'gcc' and 'objdir' are
> in the same level.
>
> 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".
>
> I don't know if we require it to execute above, specially if it's outside
the actual gcc repo.
> >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.
>
> Any solution for this> Problem still exists.
> > gl;hf, happy holidays, let us know how it went / what else you find out,
>
> Thank you and happy holidays to everyone!
> Segher
>
next prev parent reply other threads:[~2023-12-25 18:26 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
2023-12-26 14:04 ` Prashant
2023-12-25 18:26 ` Prashant [this message]
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='CAEW0Brq34=dx3DCxixV3WdyChCL_G_q3ABaqtEpTFYw3+paY4A@mail.gmail.com' \
--to=prashanthd.first@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--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).