Bug #20677: error: mach-o section specifier requires a segment whose length is between 1 and 16 characters

• Status: Open
• Assignee: kjtsanaktsidis (KJ Tsanaktsidis)
• Target version: -
• Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN

[ryandesign (Ryan Carsten Schmidt)]

ruby (the development version as of 2024-08-11) does not build on macOS 11 or earlier with Apple Clang 1300 or earlier:

coroutine/amd64/Context.S:74:14: error: mach-o section specifier requires a segment whose length is between 1 and 16 characters
.pushsection .note.gnu.property, "a"
             ^
coroutine/amd64/Context.S:86:12: error: .popsection without corresponding .pushsection
.popsection
           ^
make: *** [coroutine/amd64/Context.o] Error 1

Here is the bug I filed with MacPorts about this: https://trac.macports.org/ticket/70537

It does build on newer systems with Apple Clang 1316 or later and on older systems when using a newer llvm.org clang compiler but it would be better if a newer compiler were not required.

[mame (Yusuke Endoh)]

• Related to Bug #18061: Execshield test: libruby.so.N.N.N: FAIL: property-note test because no .note.gnu.property section found added

[mame (Yusuke Endoh)]

• Assignee set to kjtsanaktsidis (KJ Tsanaktsidis)

@kjtsanaktsidis (KJ Tsanaktsidis) Could you take a look?

[kjtsanaktsidis (KJ Tsanaktsidis)]

Ah. I might have to add some feature detection to the configure script for this when deciding if BTI/PAC is available.

Can you tell me, does it work if you compile with ASFLAGS=-fno-integrated-as?