On Thu, Jun 29, 2006 at 10:16:47AM -0500, Stephen R Marenka wrote: > On Thu, Jun 29, 2006 at 04:00:45PM +0200, Bill Allombert wrote: > > > I would like to investigate the build failure of pari (2.3.0-1) on m68k. > > (I have to say the packages was building fine with gcc 4.1.0-2 so > > I am surprised that gcc 4.1.1-2 miscompile it.
The good news is that pari 2.3.0-2 was built fine on m68k. > Are you sure? This bug has been in glibc for a while, certainly before I > reported in November. Perhaps that gcc didn't end up invoking > __USE_EXTERN_INLINES the same way. > > > Does the buildds carry the broken libc6-dev packages as well ? > > If they don't, then we have a badly outdated buildd. Well I don't understand why I cannot compile pari on crest but the autobuilder can. Toolchain package versions: crest: libc6-dev_2.3.6-15 linux-kernel-headers_2.6.17.1-1 gcc-4.1_4.1.1-5 binutils_2.16.1cvs20060413-1 buildd(tanda): libc6-dev_2.3.6-15 linux-kernel-headers_2.6.17.1-1 gcc-4.1_4.1.1-2 binutils_2.16.1cvs20060413-1 so maybe it is a gcc-4.1 issue. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
