[MacPorts] #44384: libpaper fails to build on OS X Tiger
#44384: libpaper fails to build on OS X Tiger -------------------------+-------------------------------- Reporter: djlambe11@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: tiger | Port: libpaper -------------------------+-------------------------------- When compiling libpaper (version 1.1.24) on OS X 10.4 the following error appears in the log: {{{ ... ld: unknown flag: -compatibility-version ... }}} This is due to the fact that earlier versions of OS X used {{{-dylib_compatibility_version}}}, and {{{-dylib_current_version}}}, which shows up later. The fix, then, is to patch ltmain.sh to use the {{{-dylib*}}} options where necessary. The problem with this is that the latest version of OS X I can currently run is Tiger, and I don't know when the switch was made. On the other hand, even the newest versions of OS X support the {{{-dylib*}}} options as a compatibility feature, so it doesn't harm anything to use them there. Therefore, I present a patch that enables a successful build. ---- Potentially Relevant Information: * Mac OS X 10.4.11 (Tiger) * XCode 2.5 * PowerBook G4 -- Ticket URL: <https://trac.macports.org/ticket/44384> MacPorts <http://www.macports.org/> Ports system for OS X
#44384: libpaper fails to build on OS X Tiger --------------------------+-------------------------------- Reporter: djlambe11@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: tiger Port: libpaper | --------------------------+-------------------------------- Comment (by ryandesign@…): Could you attach the main.log file from the failed build? This ticket is the only hit on Google for the search string "`unknown flag: -compatibility-version`" which makes me question the commonness of the problem or the correctness of the solution. -- Ticket URL: <https://trac.macports.org/ticket/44384#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#44384: libpaper fails to build on OS X Tiger --------------------------+-------------------------------- Reporter: djlambe11@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: tiger Port: libpaper | --------------------------+-------------------------------- Comment (by djlambe11@…): Sorry, that was me missing the shift key. It was {{{-compatibility_version}}} (noting the underscore this time). I'm uploading my main.log now. Notes, which led me to my original conclusion: From {{{man ld}}} on Tiger: {{{ -dylib_compatibility_version number ... the library is used. This option is used as the libtool(1) -compatibility_version number option when its -dynamic option is set. }}} From the man page found on the hard drive of my (broken) Mavericks machine: {{{ -compatibility_version number ... is used. This option is also called -dylib_compatibil- ity_version for compatibility. }}} with irrelevant parts shrouded behind ellipses. If you would like the full versions, I can attach them as well. It should be noted that these are taken directly from my xterm window, and the awkward hyphenation is a by-product of {{{man}}}. The 10.4 version does not have the {{{-compatibility_version}}} flag, nor the {{{-current_version}}} one. However, since my two data points are so far separated, I have no clear line to draw as to which release removed the {{{dylib_}}}. Being that the older option is still accepted should allow the patch to proceed without issue, but it would probably be better to use a conditional to only use the {{{dylib_}}} when it is strictly necessary. -- Ticket URL: <https://trac.macports.org/ticket/44384#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts