#47923: jasper @1.900.1_10 Linking error (bad option name) -------------------------+------------------- Reporter: predoehl@… | Owner: jmr@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: jasper | -------------------------+------------------- Changes (by mf2k@…): * cc: predoehl@… (removed) * owner: macports-tickets@… => jmr@… * port: => jasper Old description:

This affects my very old PowerPC system running Tiger, OS 10.4, and Xcode 2.5.

At first I could not build graphics/jasper because the linking step had two unrecognized options. Basically the build was trying to do the following:

gcc-apple-4.2 ...MANY-OPTIONS... -Wl,-compatibility_version -Wl,-current_version,2 ...

The above command failed because of the linker options, with the message, ld: unrecognized option -compatibility_version

After some research I managed to make a band-aid one-time fix by manually editing libtool in the build directory, like so:

{{{ OLD LIBTOOL OPTION NEW LIBTOOL OPTION ----------------------------------------- compatibility_version dylib_compatibility_version current_version dylib_current_version }}}

I am aware that libtool is ephemeral, created by configure, and that if I reconfigured the port, my fix would be lost. But I hope I don't need to rebuild the port often. I have no idea how to establish this fix permanently.

I do not know how to categorize the defect -- maybe it is a defect in configure, or maybe it is not a defect at all due to end-of-support for such old systems. But, I did want to report it in case it is not spurious. If I should report it elsewhere (like a GNU project mailing list), I'd be happy to, if you think it is appropriate.

New description: This affects my very old PowerPC system running Tiger, OS 10.4, and Xcode 2.5. At first I could not build graphics/jasper because the linking step had two unrecognized options. Basically the build was trying to do the following: {{{ gcc-apple-4.2 ...MANY-OPTIONS... -Wl,-compatibility_version -Wl,-current_version,2 ... }}} The above command failed because of the linker options, with the message, {{{ ld: unrecognized option -compatibility_version }}} After some research I managed to make a band-aid one-time fix by manually editing libtool in the build directory, like so: {{{ OLD LIBTOOL OPTION NEW LIBTOOL OPTION ----------------------------------------- compatibility_version dylib_compatibility_version current_version dylib_current_version }}} I am aware that libtool is ephemeral, created by configure, and that if I reconfigured the port, my fix would be lost. But I hope I don't need to rebuild the port often. I have no idea how to establish this fix permanently. I do not know how to categorize the defect -- maybe it is a defect in configure, or maybe it is not a defect at all due to end-of-support for such old systems. But, I did want to report it in case it is not spurious. If I should report it elsewhere (like a GNU project mailing list), I'd be happy to, if you think it is appropriate. -- Comment: In the future, please fill in the Port field and Cc the port maintainers ({{{port info --maintainers jasper}}}), if any. As reporter, you do not need to Cc yourself. -- Ticket URL: <https://trac.macports.org/ticket/47923#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X

#47923: apple-gcc42 @5666.3: "ld: unrecognized option -compatibility_version" when building jasper ---------------------------------+------------------------ Reporter: predoehl@… | Owner: jeremyhu@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: worksforme | Keywords: tiger Port: apple-gcc42 jasper | ---------------------------------+------------------------ Changes (by jeremyhu@…): * status: new => closed * resolution: => worksforme Comment: No response. Closing. -- Ticket URL: <https://trac.macports.org/ticket/47923#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X