#68240 closed defect (fixed)
libvorbis @1.3.7: ld: unknown options: -force_cpusubtype_ALL
| Reported by: | ddrum2000 | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.8.1 |
| Keywords: | Cc: | ||
| Port: | libvorbis |
Description
Just ran into a problem where libvorbis stops building with a linker error. I'm no expert but here are lines from the log that I think are related to the failure. Additionally I've attached the full log file.
:info:build vorbisfile.c:1992:24: warning: unused variable 'fpu' [-Wunused-variable] :info:build vorbis_fpu_control fpu; :info:build ^ :info:build ld: unknown options: -force_cpusubtype_ALL :info:build clang: error: linker command failed with exit code 1 (use -v to see invocation) :info:build make[3]: *** [test_sharedbook] Error 1 :info:build make[3]: *** Waiting for unfinished jobs....
Attachments (1)
Change History (7)
Changed 14 months ago by ddrum2000
comment:1 Changed 14 months ago by ryandesign (Ryan Carsten Schmidt)
| Summary: | libvorbis @1.3.7 - fails to build → libvorbis @1.3.7: ld: unknown options: -force_cpusubtype_ALL |
|---|
The -force_cpusubtype_ALL flag is only useful when building for PowerPC. The flag has been in the libvorbis configure.ac file since macOS support was originally added back in January 2001, prior to the release of Mac OS X 10.0: https://gitlab.xiph.org/xiph/vorbis/-/commit/e9963f888ec6d433c5850dccbeb89faf405172ad
It looks like complaining about this flag is a new problem in Xcode 15.
Here is the upstream bug report: https://gitlab.xiph.org/xiph/vorbis/-/issues/2348
comment:2 follow-up: 3 Changed 14 months ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | set to ryandesign |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:3 Changed 14 months ago by ddrum2000
So now I understand this was a known issue but could/would I go about fixing it?
Replying to ryandesign:
In e63376b0845acdc06efbfb5fbbb8bdd6359e75b4/macports-ports (master):
comment:4 Changed 14 months ago by ryandesign (Ryan Carsten Schmidt)
The way to receive this or any other fix in a MacPorts port is to wait at least an hour after the fix was committed and then run sudo port selfupdate.
comment:5 Changed 14 months ago by ddrum2000
I didn't know if there was another hack but it see the fix has been uploaded. Thanks.
main.log