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 08:08:55 +0000 [thread overview]
Message-ID: <bug-107612-4-DfqNm317x8@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
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC| |iains at gcc dot gnu.org
Last reconfirmed| |2022-12-15
Status|UNCONFIRMED |NEW
--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Rainer Orth from comment #1)
> Besides, the m2rte plugin is incorrectly named on Darwin, thus unusable:
>
> cc1gm2: fatal error: inaccessible plugin file
> /var/gcc/modula-2/10.7-gcc/./gcc/plugin/m2rte.dylib expanded from short
> plugin name m2rte: No such file or directory
> compilation terminated.
>
> There's code in gcc/jit/Make-lang.in handling the same situation.
>
> To get further along, I've just manually added a symlink for now.
Hi Rainer, you are ahead of me in testing this (I got bogged down in fixing
libffi for i686 rust use)
Just to note that the values used in gcc/jit/Make-lang.in are still not
completely correct (and that causes problems with cross-compilers where the
target and host linkers are different)
* because LD_VERSION_SCRIPT_OPTION and LD_SONAME_OPTION are for $target, not
$host.
* (maybe not relevant to gm2) the .map file is not in a format usable by
Darwin's linker and unfortunately the existing conversion scripts in the tree
do not handle that specific map.
So much of the content is useful for Darwin and mingw but those points need to
be taken into account (rather than copying verbatim).
next prev parent reply other threads:[~2022-12-15 8:08 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 [this message]
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
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-DfqNm317x8@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).