The above video goes away if you are a member and logged in, so log in now!
I was considering it, yeah. Will think about it
Are you sure of those precise "stddef.h" paths you stated earlier ?
You gave them as being:
On my Win32 system the absolute paths to those files are:
Since my PS2DEV variable is "E:\PS2_Dev" the above corresponds to internal ps2dev paths (for makefiles etc) like:
Are my paths wrong (to include the "/gcc/" part, I mean) ?
Best regards: dlanor
problem with the windows builds are that they are prefixed with a certain value, which is maybe not the same value than where you put the files at the end. That is, it depends on the guy who built the toolchain for you. One way to know is to add -v to ee-gcc when compiling something. Say I compile a hello-world.c with ee-gcc -v, I get this:
So you can see my toolchain was compiled with --prefix=/usr/local/ps2dev/ee, and thus, my ee-gcc will only work nicely when it resides in that path. Same goes with windows's toolchains. You can see the "search path is /usr/local/ps2dev/ee/lib/gcc-lib/ee/3.2.2/include".
Reading specs from /usr/local/ps2dev/ee/lib/gcc-lib/ee/3.2.2/specs
Configured with: ../configure --prefix=/usr/local/ps2dev/ee --target=ee --enable-languages=c --with-newlib --without-headers
Thread model: single
gcc version 3.2.2
/usr/local/ps2dev/ee/lib/gcc-lib/ee/3.2.2/cc1 -lang-c -v -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=2 -D__GXX_ABI_VERSION=102 -D__ELF__ -Dmips -D_mips -D__mips -D__mips__ -DR5900 -D_R5900 -D__R5900 -DR3000 -D_3000 -D__3000 -DMIPSEL -D_MIPSEL -D__MIPSEL -D__MIPSEL__ -D__ELF__ -D__mips__ -D__mips__ -D__mips -D__mips__ -D__R5900__ -D_R5900 -D__R5900 -D__R3000__ -D__3000__ -D__3000 -D__MIPSEL__ -D_MIPSEL -D__MIPSEL -D__MIPSEL__ -D__mips -D__mips -D__R5900 -D__R3000 -D__3000 -D__MIPSEL -Acpu(mips) -Amachine(mips) -D__NO_INLINE__ -D__STDC_HOSTED__=1 -D__LANGUAGE_C -D_LANGUAGE_C -DLANGUAGE_C -D_MIPS_SZPTR=32 -D_MIPS_SZINT=32 -D__SIZE_TYPE__=unsigned int -D__SSIZE_TYPE__=int -D__PTRDIFF_TYPE__=int -D_MIPS_SZLONG=64 -D__mips_fpr=64 -D_MIPS_FPSET=32 -U__mips -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS3 -D__mips=3 -D__mips64 -D__mips_eabi -D__mips_single_float -D__LANGUAGE_C__ -DLANGUAGE_C hello.c -quiet -dumpbase hello.c -version -o /tmp/ccjRZNwg.s
GNU CPP version 3.2.2 (cpplib) [AL 1.1, MM 40] (MIPSel R5900 ELF)
GNU C version 3.2.2 (ee)
compiled by GNU C version 2.95.4 20011002 (Debian prerelease).
ignoring nonexistent directory "/usr/local/ps2dev/ee/ee/sys-include"
#include "..." search starts here:
#include <...> search starts here:
End of search list.
So, just run ee-gcc.exe -v with some hello.c and see where it was configured to be installed into.