Hi Steve and LaMont, The fact is that this package DO not work on 64 bits architectures from the begining (alpha, ia64 ARE NOT in the build list of controil file). I had a lot of conversation with upstream author to improve 64bits support in the last years (give them access to my alpha...). But for the moment, the portabilitie problems are not solved, xt-aterm can be compiled but all program linked with it segv.
The only program that use the xt-* package is xt-stratego and it does not have maintainer anymore. I will orphan all my xt-* package to have more time to maintain others. Best Regards. * Steve Langasek <[EMAIL PROTECTED]> [2005-01-22 22:16:17 -0800]: > severity 291715 important > thanks > > Hi LaMont, > > Since this bug only occurs on 64-bit architectures where the package has > not been built, it doesn't appear to fit the criteria for serious bugs. > > You're right that this is a bug in debian/rules: configure is being called > with a --with-64bit argument, but the necessary CC_CC64 variable is only > defined for sparc. > > Julien, this configure option shouldn't be used at all; *all* compiler > output is 64-bit on these architectures, you should not be building the > library twice as happens when using --with-64bit. OTOH, I do also see that > there's mention in the changelog of xt-aterm being unusable on 64-bit > architectures: perhaps you want to use the -DAT_64BIT compile flag that's > mentioned in configure.in. Since past versions of xt-aterm were broken on > alpha and ia64, it may be a good idea to confirm that this fixes the problem > of misbuilt binaries before changing the package to cause binaries to be > output again on these architectures. > > -- > Steve Langasek > postmodern programmer -- Julien LEMOINE / SpeedBlue -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
