public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Sat, 31 Dec 2022 16:15:51 +0000	[thread overview]
Message-ID: <bug-107612-4-GX5BJ5E5BF@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 #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>:

https://gcc.gnu.org/g:ebc41f9a817dbae01c7450cd33c1968318ce8df0

commit r13-4939-gebc41f9a817dbae01c7450cd33c1968318ce8df0
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date:   Thu Dec 15 10:43:37 2022 +0000

    modula-2: Fix building the plugin for Darwin [PR107612].

     * Makes the configured value for INCINTL available as a variable so that
    it can be used in language makefile fragements.  It is then used in the m2
    fragment to make the include path available to the plugin compile.

     * Updates the DSO suffix  to use .dylib for Darwin.

     * Adds '-Wl,-undefined,dynamic_lookup' to the link flags so that symbols
can
       be resolved at runtime.

     * Removes the extraneous $(exeext) from the DSO names.

    Since the linking is driven by CXX, we also need to supress the addition of
    default libraries otherwise:
     (1) we will get a reference to an uninstalled libstdc++
     (2) the process opening the plugin would have two instances 0f libstdc++ -
         one statically linked into gm2 and one dynamically linked into the
plugin.

            PR modula2/107612

    gcc/ChangeLog:

            * Makefile.in: Make the configured libintl includes avaiable in
INCINTL.
            (BUILD_CPPFLAGS): Use INCINTL.

    gcc/m2/ChangeLog:

            * Make-lang.in (soext): Use .dylib for Darwin.
            (PLUGINLDFLAGS): Use dynmic lookup, set the plugin name, and append
            -nodefaultlibs to suppress the linking of libstdc++.
            Use INCINTL in compile lines for the plugin.

    Co-Authored-By: Iain Sandoe <iain@sandoe.co.uk>

  parent reply	other threads:[~2022-12-31 16:15 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
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 [this message]
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-GX5BJ5E5BF@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).