On Thu, 24 Aug 2006 at 08:01:37 +0200, Mike Hommey wrote:
> Which make me believe this might be a toolchain problem.
>
> 1.8.0.4-1 was built with:
> libc6-dev_2.3.6-13
> linux-kernel-headers_2.6.13+0rc3-2.1
> gcc-4.1_4.1.1-4
> g++-4.1_4.1.1-4
> binutils_2.16.1cvs20060413-1
> libstdc++6-4.1-dev_4.1.1-4
> libstdc++6_4.1.1-4
>
> 1.8.0.5-1 was built with:
> libc6-dev_2.3.6-18
> linux-kernel-headers_2.6.17.3-1
> gcc-4.1_4.1.1-10
> g++-4.1_4.1.1-10
> binutils_2.17-2
> libstdc++6-4.1-dev_4.1.1-10
> libstdc++6_4.1.1-10
> What would definitely make it sure it is not the toolchain would be to
> rebuild 1.8.0.4-1 with the same toolchain as 1.8.0.5-1 was built with.
> (this requires ~2GB diskspace)
The only PPCs available to me are a laptop and a machine with insufficient
RAM, but Mark Hymers has built 1.8.0.4-1 and 1.8.0.5-2 for me on a current
sid chroot; neither seems to have the bug, although it might just be that I
haven't encountered it yet. I'll keep using his build of 1.8.0.5-2 and
see whether it continues to work.
I've asked him for the version numbers of the packages you quoted on his
build machine.
Simon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
