public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/107612] plugin/m2rte doesn't build on Mac OS X 10.7 Date: Thu, 15 Dec 2022 23:29:25 +0000 [thread overview] Message-ID: <bug-107612-4-tEKBcy2NC8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107612-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107612 --- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> --- I did a little more poking - some of the missing symbols are in m2/gm2-libs-boot/libgm2.a adding that to the failing link line results in some more missing symbols, these look mainly like wrappers around libc. Slightly worrying is that find/grep seems to suggest that they might be provided from files named "glibc.xxx". Does m2 only work with glibc? (in which case there's a lot of work to do for Darwin, Windows etc)
next prev parent reply other threads:[~2022-12-15 23:29 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-10 12:48 [Bug modula2/107612] New: " ro at gcc dot gnu.org 2022-11-10 12:49 ` [Bug modula2/107612] " ro at gcc dot gnu.org 2022-11-11 9:01 ` ro at gcc dot gnu.org 2022-11-15 13:45 ` ro at gcc dot gnu.org 2022-12-15 8:08 ` iains at gcc dot gnu.org 2022-12-15 8:09 ` iains at gcc dot gnu.org 2022-12-15 8:16 ` iains at gcc dot gnu.org 2022-12-15 12:33 ` iains at gcc dot gnu.org 2022-12-15 12:46 ` iains at gcc dot gnu.org 2022-12-15 23:29 ` iains at gcc dot gnu.org [this message] 2022-12-17 0:25 ` iains at gcc dot gnu.org 2022-12-20 0:23 ` iains at gcc dot gnu.org 2022-12-31 16:15 ` cvs-commit at gcc dot gnu.org 2023-01-02 11:18 ` iains 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-107612-4-tEKBcy2NC8@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: linkBe 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).