From: Marc Glisse <marc.glisse@inria.fr>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "Matthew R. Wilson" <mwilson@mattwilson.org>,
gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Error when building gcc w/ Go language on Solaris
Date: Sat, 16 Apr 2022 21:47:27 +0200 (CEST) [thread overview]
Message-ID: <55a8308e-4538-3492-2cc-d54a9bd578bc@hippo.saclay.inria.fr> (raw)
In-Reply-To: <CAH6eHdT9cvMriLY5Ur9F1pSSR9O1b_2jBuTu3-y=ch9vRmLdDQ@mail.gmail.com>
On Sat, 16 Apr 2022, Jonathan Wakely via Gcc-help wrote:
>>> Just a guess, but maybe the Go build uses sed or another command like
>>> that, and relies on the POSIX-conforming version in /usr/xpg4/bin
>>> rather than the /usr/bin one. Try putting /usr/xpg4/bin in your path,
>>> just after /opt/mrwgcc/bin
>>
>> Aha! What a great guess -- that fixed it! Thank you so much!
>
> Great! We should document this, if we don't already. And even better would
> be if the build failed with a clear error mentioning the need for POSIX sed
> (or whichever command it was).
https://gcc.gnu.org/install/specific.html#x-x-solaris2 says
"The build process works more smoothly with the legacy Solaris tools so,
if you have /usr/xpg4/bin in your PATH, we recommend that you place
/usr/bin before /usr/xpg4/bin for the duration of the build."
So we actually document the opposite...
--
Marc Glisse
next prev parent reply other threads:[~2022-04-16 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 5:39 Matthew R. Wilson
2022-04-16 6:33 ` Jonathan Wakely
2022-04-16 19:24 ` Matthew R. Wilson
2022-04-16 19:41 ` Jonathan Wakely
2022-04-16 19:47 ` Marc Glisse [this message]
2022-04-16 23:17 ` Jonathan Wakely
2022-04-17 0:38 ` Ian Lance Taylor
2022-04-17 8:23 ` Jonathan Wakely
2022-04-19 13:36 ` Jonathan Wakely
2022-04-19 19:50 ` Ian Lance Taylor
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=55a8308e-4538-3492-2cc-d54a9bd578bc@hippo.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=mwilson@mattwilson.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).