sifadil / pcsx2-playground

Automatically exported from code.google.com/p/pcsx2-playground
2 stars 0 forks source link

Compilation on Debian Lenny x64 #138

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Compilation on Debian Lenny x64 resulted in error:

if gcc -DPACKAGE_NAME=\"ZeroGSogl\" -DPACKAGE_TARNAME=\"zerogsogl\"
-DPACKAGE_VERSION=\"0.96.2\" -DPACKAGE_STRING=\"ZeroGSogl\ 0.96.2\"
-DPACKAGE_BUGREPORT=\"zerofrog@gmail.com\" -DPACKAGE=\"ZeroGSogl\"
-DVERSION=\"0.96.2\" -DNDEBUG=1 -DRELEASE_TO_PUBLIC=1 -DZEROGS_SSE2=1
-D__x86_64__=1 -DHAVE_GL_GL_H=1 -DHAVE_GL_GLU_H=1 -DHAVE_GL_GLEXT_H=1 -I.
-I. -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12
-I/usr/include/pixman-1   -I./../ -I./../../../common -fPIC
-I/opt/cg/include -L/opt/cg/lib -O3 -fomit-frame-pointer -fpermissive 
-fPIC -I/opt/cg/include -L/opt/cg/lib -O3 -fomit-frame-pointer -fpermissive
 -MT libZeroGSLinux_a-Linux.o -MD -MP -MF
".deps/libZeroGSLinux_a-Linux.Tpo" -c -o libZeroGSLinux_a-Linux.o `test -f
'Linux.cpp' || echo './'`Linux.cpp; \
    then mv -f ".deps/libZeroGSLinux_a-Linux.Tpo"
".deps/libZeroGSLinux_a-Linux.Po"; else rm -f
".deps/libZeroGSLinux_a-Linux.Tpo"; exit 1; fi
In file included from /usr/include/sys/stat.h:107,
                 from ./../GS.h:53,
                 from Linux.cpp:25:
/usr/include/bits/stat.h:103: error: expected unqualified-id before ‘[’ 
token
/usr/include/bits/stat.h:164: error: expected unqualified-id before ‘[’ 
token

Original issue reported on code.google.com by Ragha...@gmail.com on 31 Jan 2009 at 4:01

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Sorry boys. Pcsx2 decided it would use a different directory for source files 
than I
expected, and used old version. The new version resulted in error:

-DPACKAGE_NAME=\"pcsx2\" -DPACKAGE_TARNAME=\"pcsx2\" -DPACKAGE_VERSION=\"0.9.5\"
-DPACKAGE_STRING=\"pcsx2\ 0.9.5\" -DPACKAGE_BUGREPORT=\"zerofrog@gmail.com\"
-DPACKAGE=\"pcsx2\" -DVERSION=\"0.9.5\" -DSVN_REV=\"Revision:\ 669\" -D_DEBUG=1
-DPCSX2_DEVBUILD=1 -DPCSX2_FORCESSE3=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
-DENABLE_NLS=1 -I. -I. -I./.. -I./../../   -I./../../../common/    -g -msse 
-Wall
-Wno-format -Wno-unused-value  -fpermissive -Xlinker -zmuldefs  -MT 
ix86_cpudetect.o
-MD -MP -MF ".deps/ix86_cpudetect.Tpo" -c -o ix86_cpudetect.o 
ix86_cpudetect.cpp; \
    then mv -f ".deps/ix86_cpudetect.Tpo" ".deps/ix86_cpudetect.Po"; else rm -f
".deps/ix86_cpudetect.Tpo"; exit 1; fi
In file included from ./../../System.h:26,
                 from ./../../Misc.h:22,
                 from ix86_cpudetect.cpp:22:
./../../SafeArray.h:24: warning: ‘fastcall’ attribute ignored
./../../SafeArray.h:25: warning: ‘fastcall’ attribute ignored
In file included from ./../../Misc.h:22,
                 from ix86_cpudetect.cpp:22:
./../../System.h:95: warning: ‘fastcall’ attribute ignored
./../../System.h:104: warning: ‘fastcall’ attribute ignored
./../../System.h:113: warning: ‘fastcall’ attribute ignored
./../../System.h:117: warning: ‘fastcall’ attribute ignored
./../../System.h:121: warning: ‘fastcall’ attribute ignored
./../../System.h:125: warning: ‘fastcall’ attribute ignored
ix86_cpudetect.cpp: In function ‘void cpudetectInit()’:
ix86_cpudetect.cpp:278: warning: invalid conversion from ‘s8*’ to ‘const 
char*’
ix86_cpudetect.cpp:278: warning:   initializing argument 2 of ‘int 
strcmp(const
char*, const char*)’
ix86_cpudetect.cpp:299: warning: invalid conversion from ‘s8*’ to ‘const 
char*’
ix86_cpudetect.cpp:299: warning:   initializing argument 2 of ‘int 
strcmp(const
char*, const char*)’
ix86_cpudetect.cpp: Assembler messages:
ix86_cpudetect.cpp:123: Error: suffix or operands invalid for `pop'
ix86_cpudetect.cpp:126: Error: suffix or operands invalid for `push'
ix86_cpudetect.cpp:129: Error: suffix or operands invalid for `pop'

Original comment by Ragha...@gmail.com on 31 Jan 2009 at 4:28

GoogleCodeExporter commented 8 years ago
A few notes:

* You're probably going to need those fastcall attributes working if you want to
compile pcsx2.  It relies on fastcall from a few places of the recompiler.

* The errors in ix86_cpudetect don't make sense.  Lines 123-129 on my copy of 
the
source file look like this:

--- 123 --->
   cpuid(cmd, regs[0], regs[1], regs[2], regs[3]);
   return 0;

#endif // _MSC_VER
}

<--- 129 ---

... so I think you might still have some problems on what versions of files 
you're
compiling there. :)

Original comment by Jake.Stine on 31 Jan 2009 at 10:19

GoogleCodeExporter commented 8 years ago
I think he has some old revision and here he compile assembler code before cpuid
call. The pop %%eax, push %%eax seems to be operands he could not compile.

Original comment by Zeydl...@gmail.com on 31 Jan 2009 at 11:57

GoogleCodeExporter commented 8 years ago
>cpuid(cmd, regs[0], regs[1], regs[2], regs[3]);
Exactly the same was in my source files. I'd guess it might be problem with a 
GCC 
build. I can't test it now, because I deleted /bin by an accident.

Original comment by Ragha...@gmail.com on 1 Feb 2009 at 11:49

GoogleCodeExporter commented 8 years ago
Maybe insert ".att_syntax\n" before this assembler code could help.

Original comment by Zeydl...@gmail.com on 1 Feb 2009 at 11:50

GoogleCodeExporter commented 8 years ago
One thing I noticed: "Debian Lenny x64"?

If you're on a 64-bit build of Linux, I doubt it'll compile natively. For 
various
reasons that can be found on the forums, pcsx2 playground has dropped support 
for 64
bit builds, and the code has been pulled for 64 bit support, so I doubt it 
would compile.

Pretty much the main alternatives for running it in a 64-bit environment would 
be
setting up a 32 bit chroot, and compiling it and running it in there, or just 
running
a 32 bit binary after installing the appropriate libraries.

Doing either is fairly distribution-specific, and I'm only familiar with how to 
set
up a 32-bit chroot in Gentoo. I think the steps in here would tell you how to 
set up
a 32-bit chroot in Debian, but it could be outdated, since I haven't tried it:
http://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.htm

Before you get too far in that, you should know that the recompiler is broken 
in the
latest Linux builds anyways, so until we get that fixed, you're better off with 
older
versions anyways.

If you are compiling as 32-bit, ignore all the above...

Original comment by arcum42@gmail.com on 1 Feb 2009 at 10:12

GoogleCodeExporter commented 8 years ago

Original comment by arcum42@gmail.com on 4 Feb 2009 at 8:20