How do I use the psptoolchain script?

Discuss the development of new homebrew software, tools and libraries.

Moderators: cheriff, TyRaNiD

zzzoid
Posts: 4
Joined: Thu Jan 19, 2006 7:28 pm

Post by zzzoid »

trying to use psptoolchain-20050801.tar
I keep getting the following error:
any ideas.

Code: Select all

/psp  -O2 -G0 -DPREFER_SIZE_OVER_SPEED -DCOMPACT_CTYPE -DCLOCK_PROVIDED -I/usr/local/pspdev/psp/sdk/include -fno-builtin    -O2 -g -
O2  -O2 -g -O2 -DF_isatty ../../../../../../newlib/libc/sys/psp/libcglue.c -c -o isatty.o
psp-gcc -B/tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib/ -isystem /tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib/targ-include -isys
tem /tmp/pspdev/newlib-1.13.0/newlib/libc/include -DPACKAGE=\"newlib\" -DVERSION=\"1.13.0\"  -I. -I../../../../../../newlib/libc/sys
/psp  -O2 -G0 -DPREFER_SIZE_OVER_SPEED -DCOMPACT_CTYPE -DCLOCK_PROVIDED -I/usr/local/pspdev/psp/sdk/include -fno-builtin    -O2 -g -
O2  -O2 -g -O2 -DF_time ../../../../../../newlib/libc/sys/psp/libcglue.c -c -o time.o
psp-gcc -B/tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib/ -isystem /tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib/targ-include -isys
tem /tmp/pspdev/newlib-1.13.0/newlib/libc/include -DPACKAGE=\"newlib\" -DVERSION=\"1.13.0\"  -I. -I../../../../../../newlib/libc/sys
/psp  -O2 -G0 -DPREFER_SIZE_OVER_SPEED -DCOMPACT_CTYPE -DCLOCK_PROVIDED -I/usr/local/pspdev/psp/sdk/include -fno-builtin    -O2 -g -
O2  -O2 -g -O2 -DF__link ../../../../../../newlib/libc/sys/psp/libcglue.c -c -o _link.o
psp-gcc -B/tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib/ -isystem /tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib/targ-include -isys
tem /tmp/pspdev/newlib-1.13.0/newlib/libc/include -DPACKAGE=\"newlib\" -DVERSION=\"1.13.0\"  -I. -I../../../../../../newlib/libc/sys
/psp  -O2 -G0 -DPREFER_SIZE_OVER_SPEED -DCOMPACT_CTYPE -DCLOCK_PROVIDED -I/usr/local/pspdev/psp/sdk/include -fno-builtin    -O2 -g -
O2  -O2 -g -O2 -DF__unlink ../../../../../../newlib/libc/sys/psp/libcglue.c -c -o _unlink.o
psp-gcc -B/tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib/ -isystem /tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib/targ-include -isys
tem /tmp/pspdev/newlib-1.13.0/newlib/libc/include -DPACKAGE=\"newlib\" -DVERSION=\"1.13.0\"  -I. -I../../../../../../newlib/libc/sys
/psp  -O2 -G0 -DPREFER_SIZE_OVER_SPEED -DCOMPACT_CTYPE -DCLOCK_PROVIDED -I/usr/local/pspdev/psp/sdk/include -fno-builtin    -O2 -g -
O2  -O2 -g -O2 -DF__opendir ../../../../../../newlib/libc/sys/psp/libcglue.c -c -o _opendir.o
../../../../../../newlib/libc/sys/psp/libcglue.c:248: error: syntax error before '*' token
../../../../../../newlib/libc/sys/psp/libcglue.c: In function '_opendir':
../../../../../../newlib/libc/sys/psp/libcglue.c:250: error: 'DIR' undeclared (first use in this function)
../../../../../../newlib/libc/sys/psp/libcglue.c:250: error: (Each undeclared identifier is reported only once
../../../../../../newlib/libc/sys/psp/libcglue.c:250: error: for each function it appears in.)
../../../../../../newlib/libc/sys/psp/libcglue.c:250: error: 'dirp' undeclared (first use in this function)
../../../../../../newlib/libc/sys/psp/libcglue.c:258: error: syntax error before ')' token
make[5]: *** [_opendir.o] Error 1
make[5]: Leaving directory `/tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib/libc/sys/psp'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib/libc/sys'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib/libc'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/tmp/pspdev/newlib-1.13.0/build-psp/psp/newlib'
make: *** [all-target-newlib] Error 2
ERROR BUILDING NEWLIB
I would really like to get this to work asap so I can get on with coding.
cheers
zzzoid
Posts: 4
Joined: Thu Jan 19, 2006 7:28 pm

Post by zzzoid »

It works now.

I grabbed the latest toolchain-setup from svn://svn.pspdev.org/psp/trunk/psptoolchain/

I then rinsed, and repeated. ;)

and all looks ok.

meep meep.
619619
Posts: 9
Joined: Thu Jun 30, 2005 11:02 am
Location: Italy
Contact:

Post by 619619 »

zzzoid wrote:It works now.

I grabbed the latest toolchain-setup from svn://svn.pspdev.org/psp/trunk/psptoolchain/

I then rinsed, and repeated. ;)

and all looks ok.

meep meep.
Nice, I would like to try, but...

Image

What happened to my cygwin?
I know it's (a bit) OT, but I reinstalled Cygwin enviroment 3 times (re-downloading all the files)

EDIT: A new version of cygwin have been relased, I'm going to try with that

EDIT2: The new version works with no problems
Last edited by 619619 on Fri Jan 20, 2006 9:53 pm, edited 1 time in total.
tachyon
Posts: 4
Joined: Wed Jan 18, 2006 2:52 am

Post by tachyon »

Works fine now. Just ran svn update and tried again.
User avatar
harleyg
Posts: 123
Joined: Wed Oct 05, 2005 6:15 am

Post by harleyg »

/tmp/ccDRQutU.s: Assembler messages:
/tmp/ccDRQutU.s:25: Error: illegal operands `vmidt.q M300'
make[3]: *** [sceGumLoadIdentity_vfpu.o] Error 1
make[3]: Leaving directory `/tmp/pspdev/pspsdk/src/gum'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/pspdev/pspsdk/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/pspdev/pspsdk'
make: *** [all] Error 2
ERROR BUILDING PSPSDK
im building this in a debian environment (testing/unstable), any ideas?
ooPo
Site Admin
Posts: 2023
Joined: Sat Jan 17, 2004 9:56 am
Location: Canada
Contact:

Post by ooPo »

As the readme.txt states, use 'svn update' to grab the latest version of the psptoolchain script and re-run it.
User avatar
harleyg
Posts: 123
Joined: Wed Oct 05, 2005 6:15 am

Post by harleyg »

ahh jeeze i love you, i got it on screen now :D

thanks!
kohntarkosz
Posts: 3
Joined: Tue Jan 24, 2006 9:54 pm
Location: Paris, France

Post by kohntarkosz »

Hi, sorry about first posting with a compilation problem.

I run Debian Linux Sarge. From the latest psptoochain script, the installation process stops with this output :

Code: Select all

.
aclocal: configure.ac: 19: macro `AM_PROG_AS' not found in library
configure.ac: 7: `automake requires `AM_CONFIG_HEADER', not `AC_CONFIG_HEADER'
automake: configure.ac: installing `./install-sh'
automake: configure.ac: installing `./mkinstalldirs'
automake: configure.ac: installing `./missing'
Makefile.am:35: DX_COND_doc does not appear in AM_CONDITIONAL
Makefile.am:41: DX_COND_html does not appear in AM_CONDITIONAL
Makefile.am:51: DX_COND_chm does not appear in AM_CONDITIONAL
Makefile.am:55: DX_COND_chi does not appear in AM_CONDITIONAL
Makefile.am:67: DX_COND_man does not appear in AM_CONDITIONAL
Makefile.am:77: DX_COND_rtf does not appear in AM_CONDITIONAL
Makefile.am:87: DX_COND_xml does not appear in AM_CONDITIONAL
Makefile.am:97: DX_COND_ps does not appear in AM_CONDITIONAL
Makefile.am:126: DX_COND_pdf does not appear in AM_CONDITIONAL
Makefile.am:155: DX_COND_latex does not appear in AM_CONDITIONAL
automake: Makefile.am: unterminated conditionals: @DX_COND_doc_TRUE@ @DX_COND_ht
ml_TRUE@ @DX_COND_chm_TRUE@ @DX_COND_chi_TRUE@ @DX_COND_man_TRUE@ @DX_COND_rtf_T
RUE@ @DX_COND_xml_TRUE@ @DX_COND_ps_TRUE@ @DX_COND_pdf_TRUE@ @DX_COND_latex_TRUE
@
automake: Makefile.am: unterminated conditionals: @DX_COND_doc_TRUE@ @DX_COND_ht
ml_TRUE@ @DX_COND_chm_TRUE@ @DX_COND_chi_TRUE@ @DX_COND_man_TRUE@ @DX_COND_rtf_T
RUE@ @DX_COND_xml_TRUE@ @DX_COND_ps_TRUE@ @DX_COND_pdf_TRUE@ @DX_COND_latex_TRUE
@
configure.ac: 7: required file `./[config.h].in' not found
automake: Makefile.am: warning: automake does not support EXTRA_DIST being defin
ed conditionally
Makefile.am:10: variable `DX_CONFIG' not defined
configure.ac:8: error: possibly undefined macro: AC_PSPSDK_VERSION
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:9: error: possibly undefined macro: AC_PSPDEV_PATH
configure.ac:11: error: possibly undefined macro: AM_INIT_AUTOMAKE
configure.ac:14: error: possibly undefined macro: AC_PSPDEV_TOOLCHAIN
configure.ac:19: error: possibly undefined macro: AM_PROG_AS
./configure: line 1312: AC_1.0+beta2: command not found
./configure: line 1313: AC_PSPDEV_PATH: command not found
./configure: line 1315: syntax error near unexpected token `pspsdk,'
./configure: line 1315: `AM_INIT_AUTOMAKE(pspsdk, 1.0+beta2)'
ERROR RUNNING PSPSDK CONFIGURE
autoconf 2.59 is being used. can anybody help me install the toolchain ?
jimparis
Posts: 1145
Joined: Fri Jun 10, 2005 4:21 am
Location: Boston

Post by jimparis »

kohntarkosz
Posts: 3
Joined: Tue Jan 24, 2006 9:54 pm
Location: Paris, France

Post by kohntarkosz »

thanks a lot !
Sharkus
Posts: 27
Joined: Sun Jun 19, 2005 6:49 am

Support for building GDB?

Post by Sharkus »

Is support for building psp-gdb going to be added to the perl based script? It took me a while to figure out that you needed to use the toolchain.sh script to do this...
ooPo
Site Admin
Posts: 2023
Joined: Sat Jan 17, 2004 9:56 am
Location: Canada
Contact:

Post by ooPo »

Most likely, but the perl script is currently experimental and should not be considered complete.
hubevolution
Posts: 32
Joined: Wed Mar 17, 2004 6:59 pm

Post by hubevolution »

deleted : sorry useless post !
error
Posts: 2
Joined: Sun May 07, 2006 2:56 am

What's wrong ?

Post by error »

I've got tired from this :s

I've been reading from a week to reach this state i think i'm gonna give up the PSPSDK & switching to the Lua Programming !!

but it worht asking after all anyone can tell me what's wrong ??

I'm noob here also if anyone can tell where i can find the diffrences between If I used Lua or SDKPSP tool ?

Code: Select all

Computer Scince Dept@your-0699539f8f ~/newtoolchain/newtoolchain
$ ./toolchain.pl PSP

Dependencies:
 gcc:           Found!
 make:          Found!
 wget:          Found!
 patch:         Found!
 svn:           Found!
 automake:      Found!
 autoconf:      Found!
 $PSPDEV:       Found!
 path:          Found!
 privs:         Found!

Step 1 of 6: binutils-2.16.1
 downloading:   Done!
 unpacking:     Done!
 patching:      Done!
 building:
  psp:          Error!

=====================
== ERROR DETECTED! ==
=====================

checking for psp-ld... no
checking for psp-nm... no
checking for psp-ranlib... no
checking for psp-windres... no
checking whether to enable maintainer-specific portions of Makefiles... no
checking if symbolic links between directories work... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
mkdir -p -- ./libiberty
[: Scince: unknown operand
[: Scince: unknown operand
[: Scince: unknown operand
[: Scince: unknown operand
[: Scince: unknown operand
[: Scince: unknown operand
[: Scince: unknown operand
Configuring in libiberty
/home/Computer: Can't open /home/Computer: No such file or directory
make: *** [configure-libiberty] Error 1


ERROR: Error!


Computer Scince Dept@your-0699539f8f ~/newtoolchain/newtoolchain
$
User avatar
Drakonite
Site Admin
Posts: 990
Joined: Sat Jan 17, 2004 1:30 am
Contact:

Post by Drakonite »

Try building it somewhere without spaces in the filename...
Shoot Pixels Not People!
Makeshift Development
error
Posts: 2
Joined: Sun May 07, 2006 2:56 am

Spaces ?

Post by error »

Try building it somewhere without spaces in the filename...
darko if you mean the folder name "newchaintool" there is no spaces but i'll try another folder ..

also there is no spaces in the file name --> ./toochain.pl "PSP" this is an option to use the psp toolchain because this is the new tool from oPoo site (thx man ... )


i think ...

it wants to access My Computer to reach the Console itself but it cant find the folder My Computer ??
Can't open /home/Computer: No such file or directory
i tried & created directory in the home /home/Computer ..

but i got the same error ...


thx for your reply :)

[/quote]
User avatar
Drakonite
Site Admin
Posts: 990
Joined: Sat Jan 17, 2004 1:30 am
Contact:

Re: Spaces ?

Post by Drakonite »

error wrote:
Try building it somewhere without spaces in the filename...
darko if you mean the folder name "newchaintool" there is no spaces but i'll try another folder ..
...no, I'm talking about how it says the username is "Computer Scince Dept" , which means the home dir is "/home/Computer Scince Dept", and it appears there is a problem with the spaces in the path (thus it trying to open /home/Computer) ... spaces in filenames are nasty business ;)

...if you are slightly confused, remember that ~/ is a unix shortcut that resolves to the current user's homedir, which is typically /home/username ... and IIRC unix usernames are not allowed to have spaces...

Try building it in /tmp/ , or fix the problem so you don't have those spaces ;) (spaces in filenames, while technically allowed, are Evil(TM) and can cause many problems)
Shoot Pixels Not People!
Makeshift Development
ooPo
Site Admin
Posts: 2023
Joined: Sat Jan 17, 2004 9:56 am
Location: Canada
Contact:

Post by ooPo »

My brain hurts when I try to read error's posts.
psyberjock
Posts: 28
Joined: Fri Dec 15, 2006 10:26 pm

What the hell does this mean??

Post by psyberjock »

I tried to install the toolchain (the only one available on the ps2dev.org website) and a fresh install of cygwin with all of the devel items and all of the other things that I need (wget, patch, and other unix/linux utils and some zip stuff just to be sure) and I get some stupid error. I tried it 3 times and nothing worked. I had the paths set and everything. It only crashes on GCC, I don't have any problems with the other libs. What do you think?

Image

Please help me, I have some good ideas of programs for the new USB GPS unit I just bought.

On a related note, does anyone know the functions for the USB GPS? Obviously I can't run the SDK, so I don't know what's available, if you can let me know that will help once I get the toolchain installed.

Thanks.
SamuraiX
Posts: 76
Joined: Tue Jan 31, 2006 6:28 am
Location: USA
Contact:

Post by SamuraiX »

One recommendation I can offer is when running the cygwin setup, make sure that you select all development tools and not just a few. I used to have errors a very long time ago when I first tried installing the SDK and found that the easiest solution was to install all of the dev tools/environments during cygwin setup.

And only apply the following to your cygwin.bat file after the toolchain has been installed.

Code: Select all

@echo off

C:
chdir C:\cygwin\bin

set path=%path%;C:/cygwin/usr/local/pspdev/bin
set PSPSDK=C:/cygwin/usr/local/pspdev

bash --login -i
On another note are you grabbing the latest toolchain from the svn server? Perhaps you should try to install an older toolchain.
psyberjock
Posts: 28
Joined: Fri Dec 15, 2006 10:26 pm

Post by psyberjock »

SamuraiX wrote:One recommendation I can offer is when running the cygwin setup, make sure that you select all development tools and not just a few. I used to have errors a very long time ago when I first tried installing the SDK and found that the easiest solution was to install all of the dev tools/environments during cygwin setup.

And only apply the following to your cygwin.bat file after the toolchain has been installed.

Code: Select all

@echo off

C:
chdir C:\cygwin\bin

set path=%path%;C:/cygwin/usr/local/pspdev/bin
set PSPSDK=C:/cygwin/usr/local/pspdev

bash --login -i
On another note are you grabbing the latest toolchain from the svn server? Perhaps you should try to install an older toolchain.
I did install all of the devel tools. Short of installing the complete cygwin I have everything needed for developing. It isn't giving me a file not found error. It's saying that GCC is having an internal complier error. What can I do about that?

I also tried an older toolchain and that one had different problems like the ones encountered earlier in this thread. The solution for those was to upgrade to a newer toolchain, which seems to not be an option for me.

Am I the only one who thinks that using an archaic command line system is a bad idea for development? Especially considering the number of problems that occur when people try to operate them? Why doesn't someone port the SDK to a more reliable system?

Maybe it's too late for the PSP, but in the future when another system gets a homebrew sdk, let's not use Linsux. How about Mac? I'd buy a Mac for that purpose. I've been wanting one anyway.
cory1492
Posts: 216
Joined: Fri Dec 10, 2004 1:49 pm

Post by cory1492 »

Anyone ever come across this type of problem with the .sh scripts in cygwin (its not just the toolchain, either)? It's giving me errors for blank lines, and I just am plain stumped... they were working fine a couple months ago (a few script updates ago, a few versions of prxtool ago), I really can't think of anything I would have done that could have broken it - unless, do these scripts need a specific version of perl or some other wonko thing?

Image

btw: reinstalled cygwin, tried different version of autoconf, automake, bash, added perl devel stuff... still the same thing.

edit:/ just when I ask I find a way
$ash ./toolchain.sh
instead and it goes. Guessing bash is indeed the culprit.
jimparis
Posts: 1145
Joined: Fri Jun 10, 2005 4:21 am
Location: Boston

Post by jimparis »

Given that strange output it looks like a problem with line endings. I would guess that your cygwin is configured to use "\n" as line endings, but that file contains "\r\n", and so it's looking to run a program called "\r" every time it sees a blank line.
Post Reply