Opened 3 years ago
Last modified 3 years ago
#68712 assigned defect
SuiteSparse_SPQR fails at linking stage on Sonoma ARM64 XCode 15
| Reported by: | carlodefalco | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | sonoma | Cc: | |
| Port: | SuiteSparse_SPQR |
Description
Build of many packages in the SuiteSparse (SuiteSparse_SPQR, SuiteSparse_CHOLMOD and others) suite fails in the linking stage on Sonoma ARM64 after upgrade to XCode 15.
The modified Portfile in the attachment works for me.
Attachments (1)
Change History (9)
Changed 3 years ago by carlodefalco
comment:1 Changed 3 years ago by carlodefalco
Seems the portfile was updated after my patch, still not working though. The relevant fix is just one line :
@@ -29,13 +29,14 @@ configure.optflags -O3
patch-KLU-Include-klu_version.h.diff
configure.optflags -O3
+build.args-append LDFLAGS=-ld_classic
# see https://github.com/macports/macports-ports/pull/2292#issuecomment-408526461
configure.cppflags-replace -I${prefix}/include \
-isystem${prefix}/include
comment:2 follow-up: 4 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
| Keywords: | sonoma added |
|---|---|
| Owner: | set to MarcusCalhoun-Lopez |
| Status: | new → assigned |
This flag will not cause build failures for earlier versions of Xcode/macOS?
comment:3 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
LDFLAGS usually go in configure.ldflags, not specified manually in build.args.
comment:4 Changed 3 years ago by carlodefalco
Replying to ryandesign:
This flag will not cause build failures for earlier versions of Xcode/macOS?
My other mac is completely broken so I cannot test, unfortunately :-(
But looking at the docs it seems the flag did not exist in earlier versions of the linker,
so I guess -ld_classic would be interpreted as a library name ...
comment:5 follow-up: 6 Changed 3 years ago by szhorvat (Szabolcs Horvát)
Can you check if it still fails with this draft PR? https://github.com/macports/macports-ports/pull/21451
comment:6 Changed 3 years ago by carlodefalco
Replying to szhorvat:
Can you check if it still fails with this draft PR? https://github.com/macports/macports-ports/pull/21451
What should I do to test this PR? Would I need to fork the maports-ports repo or is there a simple way?
comment:7 follow-up: 8 Changed 3 years ago by szhorvat (Szabolcs Horvát)
I think I know why this fails. It's not necessary to test at the moment. Let's hope Xcode 15.1 is released soon and fixes this.
comment:8 Changed 3 years ago by carlodefalco
Replying to szhorvat:
I think I know why this fails. It's not necessary to test at the moment. Let's hope Xcode 15.1 is released soon and fixes this.
Could you elaborate a bit? Is it a bug in the new apple that is causing this? How do you know that it will be fixed in the next bugfix release of XCode?
Modified portfile