Re: [MacPorts] #70866: gcc14 doesn’t build for x86_64 on macOS 15 (Xcode 16): “Undefined symbols for architecture x86_64” while linking libgcc_s.1.dylib
MacPorts
noreply at macports.org
Thu Sep 26 14:02:51 UTC 2024
#70866: gcc14 doesn’t build for x86_64 on macOS 15 (Xcode 16): “Undefined symbols
for architecture x86_64” while linking libgcc_s.1.dylib
---------------------------+-----------------------------------
Reporter: markmentovai | Owner: markmentovai
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: fixed | Keywords: sonoma sequoia x86_64
Port: gcc14 |
---------------------------+-----------------------------------
Comment (by markmentovai):
Replying to [comment:28 reneeotten]:
> for me it still fails even after applying the patch you linked from your
repository, but it's certainly possible that something else is going on.
Just in case, I have attached my {{{main.log}}} if that's of any help to
you.
>
> [edit: perhaps I didn't completely remove that changes to the Portfile I
already attempted; trying one more time now...]
That [https://trac.macports.org/attachment/ticket/70866/main.log.gz
main.log] ends with:
{{{
:info:build checking for suffix of object files... configure: error: in
`/opt/local/var/macports/build/_Users_renee_Software_macports-
ports_lang_gcc14/libgcc14/work/build/x86_64-apple-darwin24/libgcc':
:info:build configure: error: cannot compute suffix of object files:
cannot compile
:info:build See `config.log' for more details
:info:build make[2]: *** [configure-stage1-target-libgcc] Error 1
:info:build make[2]: Leaving directory `/opt/local/var/macports/build
/_Users_renee_Software_macports-ports_lang_gcc14/libgcc14/work/build'
:info:build make[1]: *** [stage1-bubble] Error 2
:info:build make[1]: Leaving directory `/opt/local/var/macports/build
/_Users_renee_Software_macports-ports_lang_gcc14/libgcc14/work/build'
:info:build make: *** [bootstrap-lean] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build
/_Users_renee_Software_macports-ports_lang_gcc14/libgcc14/work/build'
:info:build Command failed: cd "/opt/local/var/macports/build
/_Users_renee_Software_macports-ports_lang_gcc14/libgcc14/work/build" &&
/usr/bin/make -j8 -w bootstrap-lean
:info:build Exit code: 2
:error:build Failed to build libgcc14: command execution failed
:debug:build Error code: CHILDSTATUS 77585 2
[…]
:error:build See /opt/local/var/macports/logs
/_Users_renee_Software_macports-ports_lang_gcc14/libgcc14/main.log for
details.
}}}
That’s the telltale of #70641. It indicates that the compiler driver that
was just built does not have the `AS_NEEDS_DASH_FOR_PIPED_INPUT` fix.
If it happens again with the same `configure: error: cannot compute suffix
of object files: cannot compile`, the `config.log` at
/opt/local/var/macports/build/_Users_renee_Software_macports-
ports_lang_gcc14/libgcc14/work/build/x86_64-apple-
darwin24/libgcc/config.log will also be valuable for troubleshooting.
But at the very top of your log, I see:
{{{
:debug:main Starting logging for libgcc14 @14.2.0_1+stdlib_flag
}}}
[https://github.com/markmentovai/macports-
ports/commit/727cc2bddbd39fbad964d0f2e6eaf3be164e23e7.patch The patch]
sets `revision 2`, and the [https://github.com/macports/macports-
ports/commit/40a267e1c3265b3215fdccc45c544637e75a7557 version that Chris
committed] has a small change to put `revision 2` into effect on macOS ≥
14. Since your log shows 14.2.0_1, you must not have the patch in effect.
Since this has now been committed, you should be able to do a `port sync`
and get 14.2.0_2 without any manual effort. If you’re still having
trouble, make sure that you’ve got the correct Portfile. The SHA-256 hash
should be:
{{{
mark at arm-and-hammer zsh% shasum -a256 lang/gcc14/Portfile
6544f069e9718a8fd753f90a15340e24471485874ee0a410ddd3f1dc813be90d
lang/gcc14/Portfile
}}}
--
Ticket URL: <https://trac.macports.org/ticket/70866#comment:31>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list