[MacPorts] #69480: llvm-17 fails to build agains port:legacy-support=1.1.1 when the latter is build with -flto
MacPorts
noreply at macports.org
Thu Mar 14 13:00:12 UTC 2024
#69480: llvm-17 fails to build agains port:legacy-support=1.1.1 when the latter is
build with -flto
-----------------------------+--------------------
Reporter: RJVB | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: legacy-support |
-----------------------------+--------------------
Comment (by RJVB):
Replying to [comment:3 fhgwright]:
> This is probably a duplicate of #68314. I'm not sure about the `-flto`
part, but why don't you try again (and comment here) once `legacy-support
1.2.1` is published ([https://github.com/macports/macports-
ports/pull/23011]).
The symptoms are the same, the question is why I'm getting them when
compiling with `-flto` but without `-fPIC` (which AFAICT is the only
difference between the generated *.o and *.dl.o object files).
I can wait, of course, but I could also see if adding `-fPIC` instead of
`-fno-lto` addresses the problem without adding any others.
Do you happen to have an idea which ports link statically? Without clear
indication of significant benefits of LTO builds it's probably not worth
going down a rabbithole to fix this more properly...
BTW, `-fno-lto` overrides and disables any request to use LTO; given how
the Makefile is set up that includes any attempt of the user to obtain it
via `configure.optflags`.
(''PS: my session apparently timed out while typing this reply. Bad trac!
Thank goodness it wasn't any longer and that the browser cache didn't get
invalidated...!'')
--
Ticket URL: <https://trac.macports.org/ticket/69480#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list