Re: FTBFS: fftw3
In article <[🔎] 20040819101051.GA17674@cassis> piem@altern.org writes:
>hi all
>
>it would great if any of you could investigate why fftw3 fails [1] to
>build on sparc. following Steve's advice [2,3], we added some configure
>flags to debian/rules. it seemed to work well, except from sparc:
>
>gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../kernel -I../rdft -O3
>-fomit-frame-pointer -fno-schedule-insns -fstrict-aliasing
>-mcpu=ultrasparc -pthread -MT reodft11e-r2hc-odd.lo -MD -MP -MF
>.deps/reodft11e-r2hc-odd.Tpo -c reodft11e-r2hc-odd.c -fPIC -DPIC -o
>.libs/reodft11e-r2hc-odd.lo
>/tmp/cc9zxjF1.s: Assembler messages:
>/tmp/cc9zxjF1.s:414: Error: Illegal operands: There are only 32 single
>precision f registers; [0-31]
>/tmp/cc9zxjF1.s:756: Error: Illegal operands: There are only 32 single
>precision f registers; [0-31]
>
>i do not have access to a sparc machine, could someone have a look at
>this 3.0.1-10 ?
>
>thanks, piem
glibc fails to build with the same error. It is beleived to be a recent
binutils bug, you could reassign it there.
--
Blars Blarson blarson@blars.org
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
Reply to: