bugGNU APL - Bugs: bug #67540, Undefined symbols on macOS 12 and...

 
 

bug #67540: Undefined symbols on macOS 12 and later

Submitter:  Ryan Carsten Schmidt <ryandesign>
Submitted:  Mon 22 Sep 2025 03:17:56 AM UTC
   
 
Category:  None Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  None Privacy:  Public
Assigned to:  None Open/Closed:  Open
* Mandatory Fields

Post a Comment

Add a New Comment Rich Markup
   

Discussion

Mon 22 Sep 2025 03:05:37 PM UTC, comment #1: 

I received an email reply from Jürgen Sauermann:

> thanks a lot for providing the patch. I have applied it and
> it should be contained in SVN 1893.
>
> However, ./configure is generated (by autoconf or autoreconf),
> so it will be lost every time myself or a GNU APL user runs
> autoconf or autoreconf.
>
> I believe a cleaner way to solve this issue is that apple users
> run autoreconf on their machine to create a ./configure that
> is up-to-date with their autoconf and libtool.
>
> Before applying your patch I updated my local autoconf and libtool
> packages to the latest version in my Debian check-out (by means of
> apt-get install --reinstall). I believe that there is little more
> that I can do for apple users.
>
> Please let me know if everything works now.


Thanks.

This libtool bug was fixed in libtool 2.4.7 but another bug related to the use of the obsolete -single_module flag (https://savannah. ... g/support/?110937) wasn't fixed until 2.5.4, so please always use the latest stable versions of autoconf/automake/libtool to generate your configure script.

It's frustrating when autotools bugs persist for years after they're fixed because software developers generating configure scripts for distribution with their software don't update to fixed versions of the tools.

Looks like Debian 13 and later already have libtool 2.5.4 and Debian 12 has libtool 2.4.7. Checking Debian package sources, I have to go back to Debian 11 to find an older libtool, 2.4.6, which has a patch that fixes the bug only on macOS 11 and not on macOS 12 or later. Assuming you're on Debian 11 or earlier, can you update? Or if Debian 11 is still commonly used, do you know how we could persuade Debian to fix its libtool?

Ryan Carsten Schmidt <ryandesign>
Mon 22 Sep 2025 03:17:56 AM UTC, original submission:  

apl 1.9 fails to build on the last five years worth of macOS versions (12, 13, 14, 15, and 26).

Undefined symbol errors occur at link time because the flags "-Wl,-undefined -Wl,dynamic_lookup" have not been added.

This is due to a libtool bug which has been baked into your configure script: https://debbugs.g ... ort.cgi?bug=44605

The libtool bug has been fixed. When preparing your next release tarball, please ensure you install the latest stable version of libtool prior to generating your configure script so that this bug is not present in your tarball.

For users wanting to compile apl 1.9, or if you can't update libtool and need to fix your next configure script manually, the configure script patch is attached.

Ryan Carsten Schmidt <ryandesign>

 

Attached Files

Attached Files
file #57675:  dynamic_lookup-11.patch added by ryandesign (478B - application/octet-stream)

(Note: upload size limit is set to 4.0MiB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

 

Dependencies

This item does not depend on any other items.

No items depend on this one.

 

Mail Notification Carbon-Copy List

Carbon-Copy List
  • -email is unavailable- added by ryandesign (Submitted the item)
  •  

    Votes

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    History

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2025-09-22 ryandesign Attached File- Added dynamic_lookup-11.patch, #57675

    Back to the top

    Powered by Savane 3.16-11ef.
    Corresponding source code