Opened 9 years ago

Last modified 8 years ago

#47923 closed defect

jasper @1.900.1_10 Linking error (bad option name) — at Version 2

Reported by: predoehl@… Owned by: jmr@…
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: tiger Cc:
Port: apple-gcc42 jasper

Description (last modified by mf2k (Frank Schima))

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.

Change History (2)

comment:1 Changed 9 years ago by predoehl@…

Cc: predoehl@… added

Cc Me!

comment:2 Changed 9 years ago by mf2k (Frank Schima)

Cc: predoehl@… removed
Description: modified (diff)
Owner: changed from macports-tickets@… to jmr@…
Port: jasper added

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.

Note: See TracTickets for help on using tickets.