Re: help needed with mips build failure

Steve Langasek <[EMAIL PROTECTED]> writes: > Note that it's not sufficient for the fixed package to reach unstable, the > buildd admins also (and more importantly) need to clean up the build chroots > by manually reconciling the status of the xfree86-common package. Yeah, I'd like to think it's n

Re: help needed with mips build failure

On Wed, Feb 16, 2005 at 05:09:37PM -0800, Thomas Bushnell BSG wrote: > > That would be RC bug #295175 in the xfree86-common package. I don't imagine > > gnucash would've fared any better under these circumstances without the > > libtool update, either. > Ah, ok! I'm glad you are up on these thin

Re: help needed with mips build failure

Steve Langasek <[EMAIL PROTECTED]> writes: > That would be RC bug #295175 in the xfree86-common package. I don't imagine > gnucash would've fared any better under these circumstances without the > libtool update, either. Ah, ok! I'm glad you are up on these things; I would not have guessde to l

Re: help needed with mips build failure

On Wed, Feb 16, 2005 at 04:33:04PM -0800, Thomas Bushnell BSG wrote: > > Considering Debian is the only mainstream desktop distribution with a mips > > port, and gnucash upstream has in the past disavowed all responsibility for > > compatibility with non-i386 archs, this seems laughably false. Als

Re: help needed with mips build failure

Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: > As for it being complicated, well, I believe you. But you need not be > upstream to change the build system, I have done that three or four times > already. It is not the most gratifying work in the world, at all... but the > result is fa

Re: help needed with mips build failure

Steve Langasek <[EMAIL PROTECTED]> writes: > Considering Debian is the only mainstream desktop distribution with a mips > port, and gnucash upstream has in the past disavowed all responsibility for > compatibility with non-i386 archs, this seems laughably false. Also, > there's the fact that we'v

Re: help needed with mips build failure

On Wed, 16 Feb 2005, Thomas Bushnell BSG wrote: > Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: > > On Wed, 16 Feb 2005, Thomas Bushnell BSG wrote: > > > Now, it should be noted, upstream uses autoconf 2.13, and libtool > > > 1.4c. So these errors should not be happening, and seem to imp

Re: help needed with mips build failure

On Wed, Feb 16, 2005 at 01:02:58PM -0800, Thomas Bushnell BSG wrote: > Steve Langasek <[EMAIL PROTECTED]> writes: > > Clearly not, or it wouldn't have failed to build on mips and mipsel. There > > is nothing "perfectly working" about that version of libtool, and moreover, > > its effects are not

Re: help needed with mips build failure

Thomas Bushnell BSG wrote: > Steve Langasek <[EMAIL PROTECTED]> writes: > > > Clearly not, or it wouldn't have failed to build on mips and mipsel. There > > is nothing "perfectly working" about that version of libtool, and moreover, > > its effects are not limited to the mips architectures -- as

Re: help needed with mips build failure

[Thomas Bushnell BSG] > Perhaps mips is so rare that they wouldn't get bug reports. Perhaps. http://popcon.debian.org/ > reports: 1 0.02% kfreebsd-i386 1 0.02% ppc64 1 0.02% hurd-i386 2 0.04% mipsel 2 0.04% m68k 2 0.04% arm 4 0.07% mips 4 0.07% s39

Re: help needed with mips build failure

Steve Langasek <[EMAIL PROTECTED]> writes: > Clearly not, or it wouldn't have failed to build on mips and mipsel. There > is nothing "perfectly working" about that version of libtool, and moreover, > its effects are not limited to the mips architectures -- as the obscenely > long list of library

Re: help needed with mips build failure

On Wed, Feb 16, 2005 at 12:39:44PM -0800, Thomas Bushnell BSG wrote: > Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: > > On Wed, 16 Feb 2005, Thomas Bushnell BSG wrote: > > > Now, it should be noted, upstream uses autoconf 2.13, and libtool > > > 1.4c. So these errors should not be happ

Re: help needed with mips build failure

Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: > On Wed, 16 Feb 2005, Thomas Bushnell BSG wrote: > > Now, it should be noted, upstream uses autoconf 2.13, and libtool > > 1.4c. So these errors should not be happening, and seem to imply > > problems in the Debian auto* packages. > > Both

Re: help needed with mips build failure

On Wed, 16 Feb 2005, Thomas Bushnell BSG wrote: > Now, it should be noted, upstream uses autoconf 2.13, and libtool > 1.4c. So these errors should not be happening, and seem to imply > problems in the Debian auto* packages. Both are deprecated, outdated crap. Methinks you have some work to do to

Re: help needed with mips build failure

Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: > Steve Langasek <[EMAIL PROTECTED]> writes: > > > You're using an old (and broken) version of libtool. C.f. > > for > > Ryan's boilerplate explanation for fixing this problem. > >

Re: help needed with mips build failure

On Tue, Feb 15, 2005 at 11:30:00PM -0800, Steve Langasek wrote: >On Tue, Feb 15, 2005 at 11:22:01PM -0800, Thomas Bushnell BSG wrote: > >>Can someone with mips and/or libtool expertise examine the build >>failure for gnucash below, and see if they can diagnose the problem? > >>http://buildd.debian.

Re: help needed with mips build failure

Steve Langasek <[EMAIL PROTECTED]> writes: > You're using an old (and broken) version of libtool. C.f. > for > Ryan's boilerplate explanation for fixing this problem. Thanks a bunch, this is surely the problem, but applying the s

Re: help needed with mips build failure

On Tue, Feb 15, 2005 at 11:22:01PM -0800, Thomas Bushnell BSG wrote: > Can someone with mips and/or libtool expertise examine the build > failure for gnucash below, and see if they can diagnose the problem? > http://buildd.debian.org/fetch.php?&pkg=gnucash&ver=1.8.10-5&arch=mips&stamp=1107337123&

help needed with mips build failure

Can someone with mips and/or libtool expertise examine the build failure for gnucash below, and see if they can diagnose the problem? http://buildd.debian.org/fetch.php?&pkg=gnucash&ver=1.8.10-5&arch=mips&stamp=1107337123&file=log&as=raw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a su