macOS 15.4 Breaks All Compiles

[msintle]

Here's the build log for an empty app:

Code: Text  [Select][+][-]

1. Compile Project, Target: /Users/c/fpcupdeluxe/projects/project1: Exit code 1, Errors: 10, Warnings: 3, Hints: 2
2. Hint: Start of reading config file /Users/c/fpcupdeluxe/fpc/bin/aarch64-darwin/fpc.cfg
3. Hint: End of reading config file /Users/c/fpcupdeluxe/fpc/bin/aarch64-darwin/fpc.cfg
4. Verbose: Free Pascal Compiler version 3.2.2-r0d122c49 [2025/03/24] for aarch64
5. Verbose: Copyright (c) 1993-2021 by Florian Klaempfl and others
6. Verbose: Target OS: Darwin for AArch64
7. Verbose: Compiling /Users/c/fpcupdeluxe/projects/project1.lpr
8. Verbose: Compiling unit1.pas
9. Verbose: Assembling unit1
10. Verbose: Assembling project1
11. Verbose: Compiling resource /Users/c/fpcupdeluxe/projects/lib/aarch64-darwin/project1.or
12. Verbose: Linking /Users/c/fpcupdeluxe/projects/project1
13. Error: -macosx_version_min has been renamed to -macos_version_min
14. Warning: ld: warning: -multiply_defined is obsolete
15. Warning: ld: warning: ignoring duplicate libraries: '-lc'
16. Warning: ld: warning: no platform load command found in '/Users/c/fpcupdeluxe/projects/lib/aarch64-darwin/project1.or', assuming: macOS
17. Error: 0  0x100a741bc  __assert_rtn + 72
18. Error: 1  0x100a361b4  ld::pass::getMethods(ld::Atom const*, std::__1::vector<ld::DynamicAtomFile::ObjCMethod, std::__1::allocator<ld::DynamicAtomFile::ObjCMethod>>&) + 1244
19. Error: 2  0x100a37458  ld::pass::convertMethodListToRelative(ld::DynamicAtomFile*, std::__1::unordered_map<std::__1::basic_string_view<char, std::__1::char_traits<char>>, ld::Atom const*, std::__1::hash<std::__1::basic_string_view<char, std::__1::char_traits<char>>>, std::__1::equal_to<std::__1::basic_string_view<char, std::__1::char_traits<char>>>, std::__1::allocator<std::__1::pair<std::__1::basic_string_view<char, std::__1::char_traits<char>> const, ld::Atom const*>>>&, ld::Atom const*) + 128
20. Error: 3  0x100a33860  ld::pass::objc(ld::Options const&, ld::AtomFileConsolidator&) + 16436
21. Error: 4  0x100a5b108  ld::AtomFileConsolidator::resolve() + 13312
22. Error: 5  0x100a3b100  ld::Linker::run() + 8340
23. Error: 6  0x1009ca114  main + 1924
24. Error: ld: Assertion failed: (false && "Malformed method list"), function getMethods, file ObjC.cpp, line 150.
25. An error occurred while linking
26. Error: Error while linking
27. Verbose: There were 1 errors compiling module, stopping
28. Verbose: Compilation aborted
29. Verbose: /Users/c/fpcupdeluxe/fpc/bin/aarch64-darwin/ppca64 returned an error exitcode
30.  

Xcode Command Line Tools update broke things maybe?

Kudos to RottenApple.

[TRon]

Xcode Command Line Tools update broke things maybe?

Yes, it did. You could try trunk version of FPC. Usually such kind of issues are addressed in trunk/main and in case not then worth to report.

[msintle]

Xcode Command Line Tools update broke things maybe?

Yes, it did. You could try trunk version of FPC. Usually such kind of issues are addressed in trunk/main and in case not then worth to report.

Great to hear from you again!

Problem is that this double whammy of an "OS" update also broke the ability to boot macOS VMs, so I cannot even test trunk.

Maybe time to fire up FPCUPDLX and install Lazarus on a new folder?

[msintle]

That didn't work either:

Code: Text  [Select][+][-]

1.        Compiling univint/src/MacOSAll.pas
2. [ 65%] Compiled package univint
3. The installer encountered the following error:
4. Error inside worker thread for package rtl-objpas: Compilation of "BuildUnit_rtl_objpas.pp" failed
5. make[1]: *** [packages_smart] Error 2
6. make: *** [build-stamp.x86_64-darwin] Error 2
7.  
8. fpcupdeluxe: ERROR: FPC Native Installer (BuildModule: FPC): Error running /usr/bin/make for FPC failed with exit code 512
9. . Details: .
10.  
11.  
12. ERROR: Fpcupdeluxe fatal error !
13. Sequencer (FPC): Failure running fpcupdeluxe: error executing sequence FPC
14. Sequencer (Default): Failure running fpcupdeluxe: error executing sequence Default

On macOS 15.4 trunk RottenAppleAirBook m4.

[TRon]

The installer encountered the following error:
Error inside worker thread for package rtl-objpas: Compilation of "BuildUnit_rtl_objpas.pp" failed

Have you unchecked the "use jobs for gnu make" in setup+ prior to pressing the install button ?

make: *** [build-stamp.x86_64-darwin] Error 2

x86_64 ? The previous posted error was related to aarch64. Did you perhaps downloaded the wrong version of FPCUpDeluxe or ... ?

[Jonas Maebe]

Looks like the resource writer needs to be updated. I never was a fan of directly generating object files/machine code for this reason. I don't know if there is still an option to force the use of an external assembler for them, but I don't think so.

[msintle]

The installer encountered the following error:
Error inside worker thread for package rtl-objpas: Compilation of "BuildUnit_rtl_objpas.pp" failed

Have you unchecked the "use jobs for gnu make" in setup+ prior to pressing the install button ?

No, do I need to try like so also?

make: *** [build-stamp.x86_64-darwin] Error 2

x86_64 ? The previous posted error was related to aarch64. Did you perhaps downloaded the wrong version of FPCUpDeluxe or ... ?

Yes, I switched to the x86_64 version for diversity in testing.

[msintle]

Looks like the resource writer needs to be updated. I never was a fan of directly generating object files/machine code for this reason. I don't know if there is still an option to force the use of an external assembler for them, but I don't think so.

So this is a mandatory change we need to have for macOS 15.4 compatibility?

[msintle]

The installer encountered the following error:
Error inside worker thread for package rtl-objpas: Compilation of "BuildUnit_rtl_objpas.pp" failed

Have you unchecked the "use jobs for gnu make" in setup+ prior to pressing the install button ?

Just to follow up on this, unchecking that, and trying to install 3.2.2 + 3.4 resulted in this error:

Code: Text  [Select][+][-]

1. Compiling rtl-objpas/BuildUnit_rtl_objpas.pp
2. Compiling ./rtl-objpas/src/inc/system.uitypes.pp
3. Compiling ./rtl-objpas/src/inc/strutils.pp
4. Compiling ./rtl-objpas/src/inc/widestrutils.pp
5. Compiling ./rtl-objpas/src/common/varutils.pp
6. Compiling ./rtl-objpas/src/inc/convutils.pp
7. Compiling ./rtl-objpas/src/inc/dateutils.pp
8. Compiling ./rtl-objpas/src/inc/stdconvs.pp
9. Compiling ./rtl-objpas/src/inc/variants.pp
10. Compiling ./rtl-objpas/src/inc/fmtbcd.pp
11. Compiling ./rtl-objpas/src/inc/nullable.pp
12. Compiling ./rtl-objpas/src/inc/rtti.pp
13. rtti.pp(4361) Error: Error while assembling exitcode 1
14. rtti.pp(4361) Fatal: There were 2 errors compiling module, stopping
15. Fatal: Compilation aborted
16. rtl-objpas/units/x86_64-darwin/rtti.s:12:1: error: non-private labels cannot appear between .cfi_startproc / .cfi_endproc pairs
17. _$RTTI$_Lj102:
18. rtl-objpas/units/x86_64-darwin/rtti.s:6:1: error: previous .cfi_startproc was here
19. .cfi_startproc
20. The installer encountered the following error:
21. Compilation of "BuildUnit_rtl_objpas.pp" failed
22.  
23. fpcupdeluxe: ERROR: FPC Native Installer (BuildModule: FPC): Error running /usr/bin/make for FPC failed with exit code 512
24. . Details: .
25.  
26.  
27. ERROR: Fpcupdeluxe fatal error !
28. Sequencer (FPC): Failure running fpcupdeluxe: error executing sequence FPC
29. Sequencer (Default): Failure running fpcupdeluxe: error executing sequence Default

Strangely enough I was able to get one configuration installed successfully (even with that box checked):

3.3.1 + stable

[TRon]

Just to follow up on this, unchecking that, and trying to install 3.2.2 + 3.4 resulted in this error:

Thank you for having done so. As suspected that error was a thread related issue. It happens on occasion. If you ever see thread related errors during build remember to make sure to compile with a single thread (make names it jobs).

Code: Bash  [Select][+][-]

1. ]
2. rtl-objpas/units/x86_64-darwin/rtti.s:6:1: error: previous .cfi_startproc was here
3. .cfi_startproc
4. The installer encountered the following error:
5. Compilation of "BuildUnit_rtl_objpas.pp" failed
6.  
7. fpcupdeluxe: ERROR: FPC Native Installer (BuildModule: FPC): Error running /usr/bin/make for FPC failed with exit code 512
8. . Details: .
9. ...
10.  

Unfortunately, known issue #41045 (see the link from Jonas' reply to merge request !887 to keep track of its status)

[msintle]

Just to follow up on this, unchecking that, and trying to install 3.2.2 + 3.4 resulted in this error:

Thank you for having done so. As suspected that error was a thread related issue. It happens on occasion. If you ever see thread related errors during build remember to make sure to compile with a single thread (make names it jobs).

Code: Bash  [Select][+][-]

1. ]
2. rtl-objpas/units/x86_64-darwin/rtti.s:6:1: error: previous .cfi_startproc was here
3. .cfi_startproc
4. The installer encountered the following error:
5. Compilation of "BuildUnit_rtl_objpas.pp" failed
6.  
7. fpcupdeluxe: ERROR: FPC Native Installer (BuildModule: FPC): Error running /usr/bin/make for FPC failed with exit code 512
8. . Details: .
9. ...
10.  

Unfortunately, known issue #41045 (see the link from Jonas' reply to merge request !887 to keep track of its status)

Well I mean, how is it that only the named configuration always works, and only on 15.4 this is an issue for all other configurations?

I strongly doubt it is a threading thing to blame here.

[TRon]

I strongly doubt it is a threading thing to blame here.

These are two separate unrelated issues.

1. Build with multiple threads -> Error inside worker thread for package rtl-objpas: Compilation of "BuildUnit_rtl_objpas.pp" failed
2. Thunking -> error: previous .cfi_startproc was here

PS: The first error with aarch64 that was posted is yet another unrelated issue, see Jonas Maebe's reply.

[msintle]

So um, does anybody else see problems with Lazarus compiling (itself or your own apps) after the upgrade to Sequoia 15.4 as I am, with the single exception of the named version that seems to somehow work?

AFAIK we've already uncovered 3 issues here - are these all 15.4 specific, or do they reproduce on other versions as well?

[Nimbus]

So um, does anybody else see problems with Lazarus compiling (itself or your own apps) after the upgrade to Sequoia 15.4 as I am, with the single exception of the named version that seems to somehow work?

Not working for me either. 15.4 (24E248) / aarch64, trying to build Lazarus with fpcupdeluxe, and then the linker dies.

Code: [Select]

(9015) Linking ../lazarus
-macosx_version_min has been renamed to -macos_version_min
ld: warning: ignoring duplicate libraries: '-lc'
ld: warning: no platform load command found in '/Users/test/fpcupdeluxe/lazarus/units/aarch64-darwin/cocoa/lazarus.or', assuming: macOS
Error: (9014) Can't call the linker, switching to external linking (error was "Failed to execute "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld", error code: -11")
Fatal: (10026) There were 1 errors compiling module, stopping
make[1]: *** [ide] Error 2
make: *** [ide] Error 2
Fatal: (1018) Compilation aborted
Error: /Users/test/fpcupdeluxe/fpc/bin/aarch64-darwin/ppca64 returned an error exitcode
Error: (lazarus) Build IDE: stopped with exit code 2
Error: (lazbuild) Building IDE: Building IDE failed

fpcupdeluxe: ERROR: Lazarus Native Installer (BuildModuleCustom: UserIDE): lazbuild returned error code 512
Details: .


ERROR: Fpcupdeluxe fatal error !
Sequencer (UserIDE): Failure running fpcupdeluxe: error executing sequence UserIDE
Sequencer (Lazarus): Failure running fpcupdeluxe: error executing sequence Lazarus
Sequencer (Only): Failure running fpcupdeluxe: error executing sequence Only


[TRon]

AFAIK we've already uncovered 3 issues here - are these all 15.4 specific, or do they reproduce on other versions as well?

No, they are not all macos and/or 15.4 related specific.

The multithreaded build related issues are being taken care of, it was/is a problem on several different hosts. The second issue (.cfi_startproc ) was reported over 4 months ago and if you followed the link you can see that there is some discussion on the topic on what would be the best approach in order to solve this issue.

The 3th issue (your initial post) I have not seen mentioned before so have to guess that it is 15.4.x macos specific or perhaps better x-code tools specific (but note that this does not has to be the case, it just seems  most likely that it is).

Please report the issue, especially in case other people are able to reproduce (ask for such things so that you are not alone in this).

The worst thing that can happen is an RTFM as answer in case it is actually possible to work around the issue by using the external assembler (I have no idea how that works on/for macos and what assembler is required/supported even though all is listed in the command-line options).

Not that it matters much because no end-user seem to ever look at these reports

PS: you are not alone.