I guess this is the same bug as the one that hit me with the the lbt package.
Switching from -O3 to -O2 on m86k worked around the problem for me.
I also reported it to gcc upstream
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23160
the gcc people answered that it is not reproducible on gcc 4.1.0
This one time, at band camp, Matthias Klose said:
> Stephen Gran writes:
> > Package: gcc-4.0
> > Version: 4.0.1-2
> > Followup-For: Bug #317475
> >
> > Also see
> > http://buildd.debian.org/fetch.php?&pkg=gmp&ver=4.1.4-8&arch=m68k&stamp=1121077632&file=log&as=raw
>
> Please extract the preproces
Stephen Gran writes:
> Package: gcc-4.0
> Version: 4.0.1-2
> Followup-For: Bug #317475
>
> Also see
> http://buildd.debian.org/fetch.php?&pkg=gmp&ver=4.1.4-8&arch=m68k&stamp=1121077632&file=log&as=raw
Please extract the preprocessed source, and forward the bug report
upstream. See http://lists.de
Package: gcc-4.0
Version: 4.0.1-2
Followup-For: Bug #317475
Also see
http://buildd.debian.org/fetch.php?&pkg=gmp&ver=4.1.4-8&arch=m68k&stamp=1121077632&file=log&as=raw
Thanks,
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architect
Package: gcc-4.0
Version: 4.0.0ds2-12
Severity: normal
gcc-4.0 segfaults when building python-imaging on m68k with -O3, see log and
JpegEncode at
http://people.debian.org/~cts/gcc-4.0/
The same file compiles fine with -O2 instead of -O3.
Using built-in specs.
Target: m68k-linux
Configured with:
5 matches
Mail list logo