On 11/23/2013 06:13 AM, Philipp Kern wrote: > so this is tricky. Debian does not have any G4s left. It sounds like > a code generation issue. Could you try to use an older gcc to compile > this? And I guess it'd be helpful to get a disassembled version of the > function, so please do "disas taia_approx" in gdb and include its > output. > > Compilation will work on Debian infrastructure and the resulting > binaries will work everywhere according to your analysis. If it compiles > with an older gcc we have a sort of a workaround for people wanting to > change the code.
So, it's actually a bit more complicated than I first reported. As I mentioned, 2.1.1-6.2 will FTBFS on today's toolchain on a G4. On a G5, it will build, but when I ran it on my production setup, it ran stage 2 (a shell script whose last task is runsvdir to run gettys). The gettys start, but then runit immediately goes on to stage 3, suggesting runsvdir crashed (though I have not debugged it to confirm). I built a 2011-01-16 toolchain using snapshot.debian.net (the date the last Debian build was done) on my G5, and it does build and run correctly. It also built on the G4, but I didn't test the resulting deb. So yeah, it sounds like a code generation interaction issue with today's gcc and/or dietlibc, and is just manifesting itself in different ways on PowerPC. I'll try to do some more debugging. RF
signature.asc
Description: OpenPGP digital signature
