I'm on a Macbook Pro 1,1(1.83Ghz core duo, 2gb ram, 80gb hdd) running Leopard 10.5.4. When I run the toolchain.sh file, it won't compile the toolchain, giving an error:
I used Macports to install everything but autogen:
daxs-macbook-pro-15:~ dax$ sudo port install autogen
Password:
---> Building autogen with target all
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_autogen/work/autogen-5.9.3" && make all " returned error 2
Command output: test -f ${top_srcdir}/VERSION || die "error ${top_srcdir}/VERSION file missing"
eval `egrep '^AG_[A-Z_]*=' ${top_srcdir}/VERSION` 2> /dev/null
echo $AG_VERSION
if test ! -d "${top_srcdir}"; then
echo "NOTICE: Setting top_srcdir to .." >&2
top_srcdir=..
fi
test -f ${top_srcdir}/VERSION || die "error ${top_srcdir}/VERSION file missing"
eval `egrep '^AG_[A-Z_]*=' ${top_srcdir}/VERSION` 2> /dev/null
echo $AG_VERSION
FSM Error: in state 6 (need_value), event 8 (;) is invalid
invalid transition: in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_autogen/work/autogen-5.9.3/agen5/opts.def on line 63
token in error: `;'
[[...<error-text>]]
#ifndef XML2AG
include = <<- _END_INCLUDE
#include "autogen.
Likely causes: a mismatched quote, a value that needs quoting,
or a missing semi-colon
make[2]: *** [xmlopts.h] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Now I'm having another problem. I compiled the hello world sample(elf_template), and I don't see any text on the screen; it's just black. I'm using the above poster's already compiled SDK. I had a similar problem when I was downgrading my psp from OFW as well. Could the two be linked?
I know the pspsdk i uploaded is 100% functional. So you did something wrong. Also I dont think the pspsdk samples have been updated to work properly under the 3.xx kernel, so that may be your problem.
They work fine (except for a few very specific hack ones), but always best to be 100% sure and build any sample with: make BUILD_PRX=1 for > 3.0 kernels
TyRaNiD wrote:They work fine (except for a few very specific hack ones), but always best to be 100% sure and build any sample with: make BUILD_PRX=1 for > 3.0 kernels
No. The difference is the EBOOT has the prx instead of the elf inside. You always run the EBOOT (unless using psplink). If you're getting this error while trying to use psplink, try not using psplink. Just run the EBOOT on the PSP and see what happens.
Well for whatever reason, that compiler the other guy posted was pumping out bad eboots, so I put together a Linux VM for myself with the toolchain installed and it runs now. So I'm happy.
daxtsu wrote:Well for whatever reason, that compiler the other guy posted was pumping out bad eboots, so I put together a Linux VM for myself with the toolchain installed and it runs now. So I'm happy.
That's the best way to do it on Windows as well. :D