From: "Matthew R. Wilson" <mwilson@mattwilson.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Error when building gcc w/ Go language on Solaris
Date: Sat, 16 Apr 2022 12:24:45 -0700 [thread overview]
Message-ID: <20220416192445.dxuftlrblkhctmir@mattwilson.org> (raw)
In-Reply-To: <CAH6eHdT4FCDgvPA2T9jvQwnjchw24S7n2NKobwhdXp5O_wr6iQ@mail.gmail.com>
On 04.16.2022 07:33, Jonathan Wakely wrote:
>On Sat, 16 Apr 2022, 06:40 Matthew R. Wilson, <mwilson@mattwilson.org>
>wrote:
>
>> I am revisiting my attempts to build GCC with Go language support on
>> Solaris/SPARCv9.
>>
>> The error I get when I make is:
>> ../.././gotools/../libgo/go/cmd/go/main.go:10:16: error:
>> /export/home/mwilson/gcc-build/gcc-11.2.0/host-sparcv9-sun-solaris2.11/gcc/context.o
>> exists but does not contain any Go export data
>>
>> 3) Set my PATH to: /opt/mrwgcc:/usr/bin:/usr/sbin
>>
>> 4) configured gcc 11.2 with a similar set of options as the
>> Solaris-provided gcc:
>>
>> ./configure --prefix=/opt/mrwgcc \
>> --enable-languages=c,c++,go --enable-shared \
>> --enable-initfini-array \
>> --disable-rpath --with-system-zlib --with-build-config=no \
>> --without-gnu-ld --with-ld=/usr/bin/ld \
>> --with-gnu-as --with-as=/opt/mrwgcc/bin/as sparcv9-sun-solaris2.11
>
>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!
All the best,
Matthew
next prev parent reply other threads:[~2022-04-16 19:24 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 [this message]
2022-04-16 19:41 ` Jonathan Wakely
2022-04-16 19:47 ` Marc Glisse
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=20220416192445.dxuftlrblkhctmir@mattwilson.org \
--to=mwilson@mattwilson.org \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@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).