cyrus-sasl2: FTBFS (ppc64): /usr/bin/ld:Versions:3: syntax error in VERSION script

Andreas Jochens aj at andaco.de
Tue Oct 24 09:17:37 UTC 2006


Hello,

On 06-Oct-23 17:01, Henrique de Moraes Holschuh wrote:
> On Mon, 23 Oct 2006, Andreas Jochens wrote:
> > Would it be possible to switch the versioning off for the ppc64
> > architecture only, at least until there is another solution for this?
> > Since the package has never been built with versioned symbols on ppc64
> > anyway there would be no problem on ppc64.

> How about the ppc64 people tell us exactly what needs versioning [in
> addition to all of the library exported symbols, of course] and what needs
> not in the ppc64 ABI, and we adding a script for ppc64 versioning instead?

ppc64 would need the same symbols as the other architectures.
However, it is difficult to get the same list of symbols as on other 
architectures from the output of the nm utility because of a peculiarity 
in the ppc64 object format they are not labelled with a T (Text segment) 
but with a 'D' instead. There are also other symbols marked with a 'D'
so it is not enough to simply grep for 'D' instead to 'T'.

> Not using versioned symbols in an arch is *not* acceptable IMHO.  Doing
> arch-specific stuff to get the versioning right is quite acceptable, OTOH.
> We didn't add versioned symbols to a whole lot of libraries in Debian, sasl2
> included, for trivial reasons.

There are not that many packages which use versioned symbols. The ppc64 
port currently has problems with sasl2, libdebian-installer and the db4.x
packages. 

Symbol versioning seems to work very well for these packages, especially
for the db4.x packages. This can be seen from the fact that the etch 
release will likely use five different versions of the Berkeley db
package (db3, db4.2, db4.3, db4.4 and db4.5). Without symbol 
versioning, I guess that we would be forced to use only a single 
version of the db library. 

More to the point, I currently do not know any other solution than
switching off versioning on ppc64. I would really appreciate any ideas
to solve this problem.

Regards
Andreas Jochens



More information about the Pkg-cyrus-sasl2-debian-devel mailing list