[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [png-mng-implement] -version-number and BeOS

From: John Bowler
Subject: RE: [png-mng-implement] -version-number and BeOS
Date: Wed, 17 May 2006 03:17:21 +0100

From: Ralf Wildenhues
>What I still don't understand is the following additional change you
also suggest:
>> $ diff libpng-1.2.9beta7/ libpng-1.2.9beta11 3248c3248
>> <           current=`expr $number_major + $number_minor - 1`
>> ---
>> >           current=`expr $number_major + $number_minor`
>> 3323c3323
>> <         major=`expr $current - $age + 1`
>> ---
>> >         major=`expr $current - $age`
>There is a comment above this code that explains why this should be
necessary, no?

This is the irix/nonstopux case, I don't think there is any comment; I
able to find any explanation of why the irix case adds 1 to get the
version number.  I did notice the comment for the first case which says:

'then there is irix which has an extra 1 added just for fun'

That's clearly a reference to the second case adding of 1, not a
reference to whatever irix behaviour the second piece of code is trying
to accommodate.

The issue here is that libpng on irix has (currently) a major version
number of '0', as it does on all other operating systems.  So we need to
be able to set the major version number to 0 (currently impossible
because objects to the value of '-1' for current) and, ideally we
want to do OS specific stuff in configure to fix up the arguments to
for irix...  That would defeat the point of libtool.

Well, there is obviously something weird going on on IRIX.  libpng has
on IRIX for a long time, but maybe not with shared libraries.  Still it
weird that libtool should make a major version number of 0 impossible
and not
offer any explanation of what is going on.

John Bowler <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]