[Top][All Lists]

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

address@hidden: Re: [Mesa3d-dev] Re: libtool]

From: Sven M. Hallberg
Subject: address@hidden: Re: [Mesa3d-dev] Re: libtool]
Date: Thu, 7 Jun 2001 12:46:01 +0200
User-agent: Mutt/1.3.18i


I'm working on the Mesa project's build system using autoconf, automake, and
libtool. We're running into the following problem:

We use the formula
 version-info = Major+minor:Mesa_version:Minor
to compute proper libtool version-info from the OpenGL version number (1.2)
and our current Mesa release number (MM.Mm.Mt, e.g. 3.5.0). So, Mesa_version
is an integer derived from that release number. We'd like to use
 Mesa_version = MM * 10^4 + Mm * 10^2 + Mt
which would yield something like 30500. However libtool only accepts three
digits for the REVISION part of the version-info (as Marcelo mentions below).
Is it possible to extend that limitation to five or six digits?

That would be greatly appreciated.
Thanks in advance,


PS: Libtool rocks!

----- Forwarded message from "Marcelo E. Magallon" <address@hidden> -----

From: "Marcelo E. Magallon" <address@hidden>
To: Brian Paul <address@hidden>
Cc: address@hidden
Subject: Re: [Mesa3d-dev] Re: libtool (was CVS and SSE)
Date: Mon, 21 May 2001 23:41:40 +0200

>> Brian Paul <address@hidden> writes:

 > I'm curious why revision 30500 doesn't work.  Do you know if the revision
 > is stored as a number or a string?  I'd at least ask the libtool people why
 > 30500 doesn't work.

 because libtool defines non negative as:

    0 | [1-9] | [1-9][0-9] | [1-9][0-9][0-9]

 i.e., it not only can't start with 0, it can only have three digits.  I
 suspect this has to do with some funny test or expr implementation.  Or
 perhaps they thought three digits would be enough.  Or maybe some sick
 linker uses integers to store this info.
 Hmm... funky that '0 | [1-9]' bit...


Mesa3d-dev mailing list

----- End forwarded message -----

"Would the All-Seeing Eye please look in my direction?"
 [ KeyID........: 0xC297FEAB ]
 [ Fingerprint..: FEA5 0F93 7320 3F39 66A5  AED3 073F 2D5F C297 FEAB ]

reply via email to

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