From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Gaius Mulley <gaiusmod2@gmail.com>
Cc: 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: Tue, 12 Jul 2022 16:16:01 +0200 [thread overview]
Message-ID: <ydd1quq4dsu.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87r12qqzpb.fsf@debian> (Gaius Mulley's message of "Tue, 12 Jul 2022 13:32:00 +0100")
Hi Gaius,
> many thanks for the patch and log of the failures. I've committed the
> patch and rebuilt all Makefile.in's which are affected by m2.
thanks. I've noticed that libgm2/configure has been generated with a
patched autoconf which includes runstatedir, unlike the upstream
version. It's just a nit, but confusing.
> I think this just leaves:
>
>> * While this lets the build finish on all of i386-pc-solaris2.11,
>> sparcv9-sun-solaris2.11, and x86_64-pc-linux-gnu, I get thousands of
>> testsuite failures, all of the same kind:
>>
>> Undefined first referenced
>> symbol in file
>> RTco_signal /var/gcc/modula-2/11.4-gcc-modula-2/i386-pc-solaris2.11/./libgm2/libm2pim/.libs/libm2pim.so
>> RTco_select /var/gcc/modula-2/11.4-gcc-modula-2/i386-pc-solaris2.11/./libgm2/libm2pim/.libs/libm2pim.so
>> RTco_initSemaphore /var/gcc/modula-2/11.4-gcc-modula-2/i386-pc-solaris2.11/./libgm2/libm2pim/.libs/libm2pim.so
>> RTco_wait /var/gcc/modula-2/11.4-gcc-modula-2/i386-pc-solaris2.11/./libgm2/libm2pim/.libs/libm2pim.so
>> ld: fatal: symbol referencing errors
>> collect2: error: ld returned 1 exit status
>> compiler exited with status 1
>> FAIL: gm2/exceptions/run/pass/libexcept.mod compilation, -g
>>
>> I haven't yet tried to fix those.
>
> which I'll try and reproduce,
Excellent. I've also seen this one on Linux/x86_64, so this isn't a
Solaris-specific issue.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2022-07-12 14:16 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
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 [this message]
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=ydd1quq4dsu.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gaiusmod2@gmail.com \
--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).