public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/107630] New: runtime libs should be self-contained
Date: Fri, 11 Nov 2022 09:12:05 +0000 [thread overview]
Message-ID: <bug-107630-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107630
Bug ID: 107630
Summary: runtime libs should be self-contained
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: modula2
Assignee: gaius at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
Target Milestone: ---
Prompted by PR modula2/107629, I checked the runtime libs on Solaris and Linux,
and (not unexpectedly) found the same issue: with the exception of libm2min.so,
none of the gm2 runtime libs are self-contained, each containing tons of
undefined
references. This is considered bad style at least (cf. the libtool manual,
among others), and with a small (and intentional) exception in libgo.so, all
other gcc runtime libs are, as they should be.
It would be good if libgm2 would follow suite, making PR modula2/107629
vanish.
I've had a quick look myself, but things seem not so easy since some of the
unresolved symbols are defined in several of the other runtime libs, plus there
are references to completely difference libs (libm2pim -> libstdc++) or objects
(libm2pim -> gm2-gcc/init.o).
next reply other threads:[~2022-11-11 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 9:12 ro at gcc dot gnu.org [this message]
2023-03-15 23:20 ` [Bug modula2/107630] " gaius at gcc dot gnu.org
2023-03-15 23:31 ` gaius at gcc dot gnu.org
2023-03-15 23:36 ` gaius at gcc dot gnu.org
2023-03-16 20:37 ` cvs-commit at gcc dot gnu.org
2023-03-22 1:46 ` cvs-commit at gcc dot gnu.org
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=bug-107630-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).