Help with psptoolchain on leopard....

[cloudpjff7]

Can anyone walk me through installing the psptoolchain on leopard? I've tried both of the tutorials I've seen, one here, and one on qj.net, but neither seem to work. Thank you in advance.
Edit:
When I type in:

Code: Select all

sudo port install autogen autoconf2.5 automake1.8 libtool make svn-client wget sdl libtool14

Into terminal I get this error:

Code: Select all

--->  Building guile 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_lang_guile/work/guile-1.8.3" && make all " returned error 2
Command output:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I/opt/local/include -D_THREAD_SAFE -O2 -Wall -Wmissing-prototypes -Werror -MT libguile_la-fports.lo -MD -MP -MF .deps/libguile_la-fports.Tpo -c fports.c  -fno-common -DPIC -o .libs/libguile_la-fports.o
cc1: warnings being treated as errors
fports.c: In function 'scm_open_file':
fports.c:364: warning: implicit declaration of function 'open64'
fports.c: At top level:
fports.c:614: error: syntax error before 'fport_seek_or_seek64'
fports.c:614: error: syntax error before 'off64_t'
fports.c:615: warning: return type defaults to 'int'
fports.c:615: warning: no previous prototype for 'fport_seek_or_seek64'
fports.c: In function 'fport_seek_or_seek64':
fports.c:616: error: 'port' undeclared (first use in this function)
fports.c:616: error: (Each undeclared identifier is reported only once
fports.c:616: error: for each function it appears in.)
fports.c:618: error: 'off64_t' undeclared (first use in this function)
fports.c:618: error: syntax error before 'rv'
fports.c:623: error: 'offset' undeclared (first use in this function)
fports.c:623: error: 'whence' undeclared (first use in this function)
fports.c:626: error: 'result' undeclared (first use in this function)
fports.c:626: error: 'rv' undeclared (first use in this function)
fports.c:626: warning: implicit declaration of function 'lseek64'
fports.c: In function 'fport_seek':
fports.c:677: error: 'off64_t' undeclared (first use in this function)
fports.c:677: error: syntax error before 'rv'
fports.c:678: error: 'rv' undeclared (first use in this function)
fports.c: In function 'scm_i_fport_truncate':
fports.c:711: warning: implicit declaration of function 'ftruncate64'
make[3]: *** [libguile_la-fports.lo] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Error: The following dependencies failed to build: guile
Error: Status 1 encountered during processing.

Thx for the help, sorry about my earlier post.

[Wally]

an error message would be nice :)

[Oguz286]

That's like asking "My computer broke down. Can you fix it?" without telling WHAT the problem is, so yeah, what Wally4000 said ;)

[flynn_nrg]

Like others have said, what's the problem you're experiencing? I'm using the PSPSDK on Leopard and it works fine, like it did on Tiger before. The only issue you might encounter is libusb related. The one installed by Fink doesn't work. There's a pkg floating around that will do, even although is tagged as a Tiger package.

[Wally]

For some reason I don't think he'll be back for a few weeks.

Maybe someone could compile and upload for the poor fella!

I wonder what sort of devving hes doing

[cloudpjff7]

I'm sorry, I was in los Angeles, and I updated my post thanks for the help.

[Wally]

update macports, see how that goes.

[cloudpjff7]

I updated and got past that issue however when isntalling autogen I get this error:

Code: Select all

--->  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:   emulate sh
  NULLCMD=:

else case `set -o` in *posix*) set -o posix ;; esac
fi

for f in 1 2 5 6 7 13 14
do trap "echo trapped on $f >&2" $f ; done

test -n "${CDPATH}" && {
  CDPATH=''
  unset CDPATH
}
( unalias cd ) 1>&2 && unalias cd
die() {
  echo "Killing AutoGen:  $*" >&8
  kill -TERM ${AG_pid}
  exit 1
}
exec 2>&8
AG_pid=71319


echo
echo ShElL-OuTpUt-HaS-bEeN-cOmPlEtEd - 1
AutoGen aborting on signal 10 (Bus error) in state LOAD_DEFS
/bin/sh: line 1: 71319 Abort trap              /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_autogen/work/autogen-5.9.3/agen5/autogen -L../autoopts --definition=./xmlopts.def
make[2]: *** [xmlopts.h] Error 134
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Error: Status 1 encountered during processing.

I've tried, the following:
sudo port selfupdate, sudo port clean autogen, sudo port install autogen

But it doesn't seem to work, thx.

[Wally]

im sure its not autogen, autogen is fine.. its usually either autoconf or automake :)

[cloudpjff7]

ok, that problem solved. However, when I run:

Code: Select all

sudo ./toolchain.sh

I get this error:

Code: Select all

ERROR: Set $PSPDEV before continuing.
../depends/check-pspdev.sh: Failed.

I'm sure I set it I ran the export PSPDEV command and such.
Any answers?

[Wally]

make sure the export stuff is in your .bash_profile file.

type

Code: Select all

sudo pico .bash_profile

in terminal (make sure you are in your home directory) and edit it into there, just remember to save it (control x then y)

I have this in mine currently:

export PSPDEV=/usr/local/pspdev
export PATH="/bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin/:/usr$

close terminal and reopen it then try that command again.

[jimparis]

ok, that problem solved. However, when I run:

Code: Select all

sudo ./toolchain.sh

I get this error:

Code: Select all

ERROR: Set $PSPDEV before continuing.
../depends/check-pspdev.sh: Failed.

I'm sure I set it I ran the export PSPDEV command and such.
Any answers?

Use sudo ./toolchain-sudo.sh

[J.F.]

Can you chown directories in OSX? Chowning the directory avoids all that sudo nonsense. I would say to drop the sudo part of the toolchain and just start telling people to chown the pspsdk directory. They'll have less trouble in the long run, and you won't have to worry about maintaining two scripts.

[ooPo]

Inside toolchain-sudo.sh you'll see it is just a wrapper that sets a few environment variables, like $PATH and $PSPDEV, because sudo trashes them to maintain a secure environment. It then calls toolchain.sh. There's no need to maintain two scripts - toolchain-sudo.sh never has to change.

Getting people to chown directories is problematic because people don't like to read directions, or follow them if they do. The more automatic it is the less likely a user will have problems.

[J.F.]

Inside toolchain-sudo.sh you'll see it is just a wrapper that sets a few environment variables, like $PATH and $PSPDEV, because sudo trashes them to maintain a secure environment. It then calls toolchain.sh. There's no need to maintain two scripts - toolchain-sudo.sh never has to change.

Getting people to chown directories is problematic because people don't like to read directions, or follow them if they do. The more automatic it is the less likely a user will have problems.

That's good about the script, but not chowning a directory is simply putting off the complaint until later. The first time they try to compile their own lib, we'll have yet another thread whining because they forgot to sudo before doing make install, or even worse, the make relies on envvars that sudo doesn't preserve as you mention in the sudo script. They'll be whining about how the sudo make install wrote the lib and include files to the wrong place.

[ooPo]

Well, we can certainly add instructions in the readme to describe how to make/chown the directory before running toolchain.sh. It used to be that way and it worked well for most people. You're right, it is the better way...

But, we can also leave toolchain-sudo.sh around for those who don't want to read. :)

Sound good?

[J.F.]

Yep! Sounds great. Sorry to be a pain about it.

[cloudpjff7]

Hey, thanks for the help everyone, I made it through that error....
However, after it runs for about an hour I get this:

Code: Select all

../../gcc/config/rs6000/host-darwin.c:38: warning: ‘struct sigaltstack’ declared inside parameter list
../../gcc/config/rs6000/host-darwin.c:38: warning: its scope is only this definition or declaration, which is probably not what you want
../../gcc/config/rs6000/host-darwin.c:38: error: conflicting types for ‘sigaltstack’
/usr/include/signal.h:89: error: previous declaration of ‘sigaltstack’ was here
../../gcc/config/rs6000/host-darwin.c: In function ‘segv_handler’:
../../gcc/config/rs6000/host-darwin.c:71: error: ‘struct __darwin_mcontext’ has no member named ‘ss’
../../gcc/config/rs6000/host-darwin.c:120: error: ‘struct __darwin_mcontext’ has no member named ‘es’
../../gcc/config/rs6000/host-darwin.c:120: error: ‘struct __darwin_mcontext’ has no member named ‘ss’
../../gcc/config/rs6000/host-darwin.c: In function ‘darwin_rs6000_extra_signals’:
../../gcc/config/rs6000/host-darwin.c:134: warning: passing argument 1 of ‘sigaltstack’ from incompatible pointer type
make[2]: *** [host-ppc-darwin.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [all-gcc] Error 2
make: *** [all] Error 2
../scripts/002-gcc-4.1.0-stage1.sh: Failed.
ERROR: Could not run the toolchain script.

Any tips?