[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: FTBFS: fftw3



On Thu, 19 Aug 2004 08:55:25 -0400
Ben Collins <bcollins@debian.org> wrote:

> On Thu, Aug 19, 2004 at 12:10:51PM +0200, Paul Brossier wrote:
> > 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
> 
> That -mcpu=ultrasparc thing is your problem. Building like that means it
> wont run on sparc32 systems, and that's a bug. Figure out why it is
> trying to use those flags (especially when the buildd forces a sparc32
> like environment, which should keep this from happening).

Using -mcpu=ultrasparc is wrong for binaries which need to work
on sparc32, that's correct.

But the build failure is real, and needs to be fixed independantly.
As mentioned in other emails, it's most likely a binutils bug since
glibc builds are failing similarly.



Reply to: