From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Gaius Mulley via Gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Modula-2: merge followup (brief update on the progress of the new linking implementation)
Date: Mon, 11 Jul 2022 13:14:08 +0200 [thread overview]
Message-ID: <yddo7xvaolb.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <yddwnck9i14.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Mon, 11 Jul 2022 10:21:11 +0200")
Hi Gaius,
>> A very brief update to say that I've merged the new linking
>> implementation back onto the devel/modula-2 branch,
>
> unfortunately, that branch doesn't bootstrap for me anywere:
[...]
> * On sparc-sun-solaris2.11:
[...]
> Seems like PR modula2/101392 raised its ugly head again, after it had
> been gone for a while. I'm currently trying sparcv9-sun-solaris2.11
> instead to see how that fares.
as expacted the Solaris/sparcv9 bootstrap got into building the target
libs, then failing in the same way as on Solaris/x86 and Linux/x86_64.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2022-07-11 11:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 10:31 Gaius Mulley
2022-07-11 8:21 ` Rainer Orth
2022-07-11 11:14 ` Rainer Orth [this message]
2022-07-11 15:06 ` Gaius Mulley
2022-07-11 20:36 ` Rainer Orth
2022-07-12 12:32 ` Gaius Mulley
2022-07-12 14:16 ` Rainer Orth
2022-07-25 9:42 ` Gaius Mulley
2022-07-26 7:45 ` Rainer Orth
2022-08-30 11:03 ` Gaius Mulley
2022-08-30 12:44 ` Martin Liška
2022-08-30 15:36 ` Gaius Mulley
2022-08-31 9:54 ` Martin Liška
2022-08-31 13:19 ` Gaius Mulley
2022-08-31 13:25 ` Martin Liška
2022-09-01 12:22 ` Gaius Mulley
2022-09-07 12:29 ` Martin Liška
2022-09-08 15:52 ` Gaius Mulley
2022-09-09 12:16 ` Martin Liška
2022-09-09 15:40 ` Gaius Mulley
-- strict thread matches above, loose matches on Subject: below --
2022-06-11 19:15 Gaius Mulley
2022-06-17 17:08 ` Gaius Mulley
2022-06-17 19:02 ` Richard Biener
2022-06-27 7:24 ` Gaius Mulley
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=yddo7xvaolb.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@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).