[MacPorts] #61243: libtool @2.4.6_9: link mode ignores specified compiler
MacPorts
noreply at macports.org
Sun Apr 21 22:11:22 UTC 2024
#61243: libtool @2.4.6_9: link mode ignores specified compiler
---------------------------+----------------------
Reporter: chrstphrchvz | Owner: larryv
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.6.3
Resolution: | Keywords:
Port: libtool |
---------------------------+----------------------
Comment (by ryandesign):
Has duplicate #43005.
Christopher, thanks for those links. I've read through them.
Replying to [comment:2 chrstphrchvz]:
> https://openwrt-devel.openwrt.narkive.com/dakgoLUj/cross-libtool
This thread from 2012 is indeed a user reporting this problem and it is
suggested that libtool is being used incorrectly but it is never clarified
in what way it is being used wrong. The few suggested solutions are
disproven by the OP.
>
https://web.archive.org/web/20210210153259/metastatic.org/text/libtool.html
The second problem on that page from 2007, "The wrong-gcc problem", does
describe this problem. The first solution presented there, using `-rpath`,
does not sound relevant to me but I have not tried it. The second
solution, building a dedicated libtool for each compiler that you want to
use and instructing each build to use it, sucks. There is no reference to
any upstream bug report or discussion.
Replying to [comment:3 chrstphrchvz]:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=11911
This bug from 2012 talks about unknown arguments passed to libtool when
linking being ignored but doesn't mention the wrong compiler being used to
do the link. If this is indeed the same problem, the developers of libtool
may not recognize its severity given this lack of information.
I think a new bug report should be filed with the developers of libtool.
--
Ticket URL: <https://trac.macports.org/ticket/61243#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list