From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Gabriele Bulfon via Gcc <gcc@gcc.gnu.org>
Subject: Re: Build of any gcc breaks on my sparc / illumos env
Date: Tue, 05 Jul 2022 20:04:33 +0200 [thread overview]
Message-ID: <ydd1quzcu6m.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <950112217.7047.1657042720342@www> (Gabriele Bulfon via Gcc's message of "Tue, 5 Jul 2022 19:38:40 +0200 (CEST)")
Hi Gabriele,
> Hi, took me some time to get back to this.
> The reason why I need to build new gccs is that to build latest illumos
> gate I need gcc7 and gcc10 together.
> The illumos gate that I can build with illumos gcc 4.4.4 is around 2019, so
> I tried backporting latest ld, libld, libelf, liblddbg sources to my 2019
> gate and rebuilt only these components manually, than installed bin and
> libs manually.
> The problem persists. Is there any other components I need to backport?
> Using ldd I see only these dependencies for ld.
no matter if you just want to build openindiana userland or the illumos
core, you will have no luck with unpatched upstream GCC: the
Illumos/OpenIndiana guys are keeping a large set of patches that have
never been upstreamed and are almost certainly required to get a working
gcc on Illumos, let alone one that is capable of building Illumos ON.
If at all, you should be starting from the oi-userland repo
(cf. components/developer/gcc-*) and check which version of GCC (beyond
the heavily patched gcc 4.4.4) is required to build Illumos. Besides,
SPARC support has been removed from Illumos completely some time ago, so
you're pretty much on your own here. You may have some luck getting
hints from Peter Tribble of Tribblix fame who provided a SPARC version
of his distribtion until August 2018.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2022-07-05 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 10:13 Gabriele Bulfon
2022-06-20 11:04 ` Joel Sherrill
2022-06-20 11:23 ` Gabriele Bulfon
2022-06-20 13:21 ` Joel Sherrill
2022-06-20 16:09 ` Gabriele Bulfon
2022-06-21 11:44 ` Joel Sherrill
2022-07-05 17:44 ` Gabriele Bulfon
2022-06-21 7:39 ` Eric Botcazou
2022-07-05 17:38 ` Gabriele Bulfon
2022-07-05 18:04 ` Rainer Orth [this message]
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=ydd1quzcu6m.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc@gcc.gnu.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).