Changes between Initial Version and Version 1 of Ticket #61406


Ignore:
Timestamp:
Nov 4, 2020, 9:32:57 PM (4 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

There are several other reports of this problem by searching Google.

Here is the upstream bug report, I think: ​https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36172

The problem occurs because Xcode 11 has the macOS 10.15 SDK. Aligned alloc was apparently introduced in 10.15 and the emacs configure script erroneously takes it presence in the SDK as an indication that it can be used at runtime on 10.14, which it cannot. The developers of emacs appear to be unaware of how macOS SDKs work.

You could avoid the problem by downgrading to Xcode 10 and the Xcode 10 version of the command line tools.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #61406

    • Property Status changed from new to assigned
    • Property Summary changed from Emacs 27.1_2 +x11 fails to build with undefined symbol to emacs @27.1_2+x11: dyld: lazy symbol binding failed: Symbol not found: _aligned_alloc
    • Property Owner set to drkp
    • Property Keywords emacs +x11 removed
    • Property Port emacs added; emacs@27.1_2+x11 removed

  • Ticket #61406 – Description

    initial v1  
    33I have so far been unable to build any version of Emacs 27 +x11.  I keep getting this message during bootstrap build:
    44
     5{{{
    56:info:build ./temacs --batch  -l loadup --temacs=pbootstrap
    67:info:build dyld: lazy symbol binding failed: Symbol not found: _aligned_alloc
    … …  
    910emacs/work/emacs-27.1/src/./temacs
    1011:info:build   Expected in: /usr/lib/libSystem.B.dylib
     12}}}
    1113
    1214I can successfully build emacs 27.1_2 W/O x11, but I am a heavy X11 user and prefer that variant.
    1315I have also successfully built emacs 26+x11.
    1416
    15 macOS 10.14.6 Mojave
     17macOS 10.14.6 Mojave\\
    1618Xcode 11.3.1