Re: Mupen64 FTBFS on Sparc
On 5/9/06, Gonéri Le Bouder <goneri@rulezlan.org> wrote:
On Monday 08 May 2006 23:24, Ryan Schultz wrote:
> On Monday 08 May 2006 15:02, you wrote:
> > On 5/7/06, Ryan Schultz <schultz.ryan@gmail.com> wrote:
> > IIRC, the default optimisation that should be used in Debian packages
> > should be O2, not O3; also, there are some restriction regarding the
> > compilation flags which are allowed because the package should build
> > on all supported arches.
>
> True; these are just upstream's default flags. I'll enforce correct flags
> when I handle the -DX86 in the debian/rules.
>
> Has anyone done a test built on a non-x86 arch with -DX86 off to ensure
> that mupen64 builds as it should?
I try the build with -02 (instead of -DX86 -03):
Does that means that I am absolved of building it on ppc? :-)
(snip)
r4300/x86/gcop0.o r4300/x86/gcop0.c
gcc -O2 -fomit-frame-pointer -ffast-math -fno-strict-aliasing -fPIC -Wall -pipe -c -o
r4300/x86/assemble.o r4300/x86/assemble.c
gcc -O2 -fomit-frame-pointer -ffast-math -fno-strict-aliasing -fPIC -Wall -pipe -c -o
r4300/x86/gcop1.o r4300/x86/gcop1.c
gcc -O2 -fomit-frame-pointer -ffast-math -fno-strict-aliasing -fPIC -Wall -pipe -c -o
r4300/x86/gcop1_s.o r4300/x86/gcop1_s.c
gcc -O2 -fomit-frame-pointer -ffast-math -fno-strict-aliasing -fPIC -Wall -pipe -c -o
r4300/x86/gcop1_d.o r4300/x86/gcop1_d.c
gcc -O2 -fomit-frame-pointer -ffast-math -fno-strict-aliasing -fPIC -Wall -pipe -c -o
r4300/x86/gtlb.o r4300/x86/gtlb.c
gcc -O2 -fomit-frame-pointer -ffast-math -fno-strict-aliasing -fPIC -Wall -pipe -c -o
r4300/x86/gregimm.o r4300/x86/gregimm.c
gcc -O2 -fomit-frame-pointer -ffast-math -fno-strict-aliasing -fPIC -Wall -pipe -c -o
r4300/x86/gspecial.o r4300/x86/gspecial.c
gcc -O2 -fomit-frame-pointer -ffast-math -fno-strict-aliasing -fPIC -Wall -pipe -c -o
r4300/x86/gcop1_w.o r4300/x86/gcop1_w.c
gcc -O2 -fomit-frame-pointer -ffast-math -fno-strict-aliasing -fPIC -Wall -pipe -c -o
r4300/x86/debug.o r4300/x86/debug.c
gcc -O2 -fomit-frame-pointer -ffast-math -fno-strict-aliasing -fPIC -Wall -pipe -c -o
r4300/x86/rjump.o r4300/x86/rjump.c
{standard input}: Assembler messages:
{standard input}:60: Error: Illegal operands
{standard input}:64: Error: Illegal operands
{standard input}:93: Error: Illegal operands
make[1]: *** [r4300/x86/rjump.o] Error 1
make[1]: Leaving directory `/tmp/buildd/mupen64-0.5.dfsg'
make: *** [build-stamp] Error 2
pbuilder: Failed autobuilding of package
What I find weird is that all of these are under an x86 directory!?
Isn't this arch dependant code?
--
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein
Reply to: