[MacPorts] #40155: serf1 @1.3.1: Build fails on PPC Tiger (Mac OS X 10.4.11) due to "more than one: -compatibility_version option specified"

[MacPorts]

#40155: serf1 @1.3.1: Build fails on PPC Tiger (Mac OS X 10.4.11) due to "more than
one: -compatibility_version option specified"
------------------------------+---------------------
  Reporter:  Peter_Dyballa@…  |      Owner:  blair@…
      Type:  defect           |     Status:  new
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.2.99
Resolution:                   |   Keywords:  tiger
      Port:  serf1            |
------------------------------+---------------------

Comment (by mp@…):

 Replying to [comment:26 ryandesign@…]:
 > The problem is that the build system uses more than one
 `-compatibility_version` option. The old libtool on Tiger complains about
 this. The new libtool on newer OS X silently ignores one of them. The fix
 should be to remove the duplicate option that's not being used.

 Removing the duplicate option is exactly what this patch does, letting
 scons take care of it.

 > That doesn't appear to be what the patch attached to this ticket does.
 The patch seems to remove the `-compatibility_version` option that's
 actually relevant, causing the build to then fall back on the option that
 was previously being ignored, which has the wrong values, which cause all
 the issues you mentioned above. So that's not what we want.

 No, it sets SHLIBVERSION to the correct value (MINOR+1).

 > The problem is that I only see one occurrence of
 `-compatibility_version` in the source, in the SConstruct, and that's the
 one we want to use. Where is the one we don't want to use coming from? Is
 scons inserting that itself? If so we need to figure out how to suppress
 that or tell it to use the values we want instead of the wrong values it
 thinks we want.

 Basically, the idea with this patch is to allow scons to handle the
 -compatibility/current_version by setting
 {{{
   env['SHLIBVERSION']='${%d}.0.0' % (MINOR+1,)
 }}}
 so that it's not set twice.\\
 A more thorough explanation is in comment:13.

 It works correctly on 10.4, and according to comment:22 also on 10.7. (The
 libversion increase mentioned comment:22 might be because SHLIBVERSION was
 set to 3.0.0 and the -compatibility/current_version to 4.0.0, apparently
 causing the 3.0.0 to be used. I don't have 10.7 to confirm this cause, so
 it's just a theory.)

-- 
Ticket URL: <https://trac.macports.org/ticket/40155#comment:27>
MacPorts <http://www.macports.org/>
Ports system for OS X