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/107629] New: runtime libs don't link on macOS
Date: Fri, 11 Nov 2022 09:05:57 +0000	[thread overview]
Message-ID: <bug-107629-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107629

            Bug ID: 107629
           Summary: runtime libs don't link on macOS
           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: ---
              Host: x86_64-apple-darwin11.4.2
            Target: x86_64-apple-darwin11.4.2
             Build: x86_64-apple-darwin11.4.2

The gm2 runtime libs don't link on macOS, e.g. libm2log:

Undefined symbols for architecture x86_64:
  "_DynamicStrings_ConCat", referenced from:
      _FileSystem_Create in FileSystem.o
      _InOut_OpenInput in InOut.o
      _InOut_OpenOutput in InOut.o
      _RealConversions_LongRealToString in RealConversions.o
      _Pad.part.0 in RealInOut.o
      _Strings_Delete in Strings.o
      _Strings_Insert in Strings.o
      ...

and many more.

While libtool knows about the ld option to lift that requirement, there seems
to be no way to activate it.  For now, I've just manually added

LDFLAGS = -Wl,-undefined -Wl,dynamic_lookup

to the various libgm2 Makefiles.  I suspect something along the lines of
libitm/configure.tgt or libsanitizer/configure.tgt will be necessary to handle
this for real.  However, the best way would be to make the libs self-contained,
actually, so the issue would just vanish.

             reply	other threads:[~2022-11-11  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  9:05 ro at gcc dot gnu.org [this message]
2022-11-11  9:06 ` [Bug modula2/107629] " ro at gcc dot gnu.org
2022-11-15 13:51 ` ro at gcc dot gnu.org
2023-01-17 15:22 ` 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-107629-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).