Assembler problems installing

UsefulIdiot · Post by **UsefulIdiot** » Tue Jan 17, 2006 4:52 pm

I found a spare box today to do my psp dev'ing on and installed ubuntu on it(dont like messing with cygwin). I installed all the required packages and the sdk seems to compile fine until (i think) its linking sceGumLoadIdentity.o

The assembler outputs the error:

/tmp/ccapdkp6.s: Assembler error:

/tmp/ccapdkp6.s:25: Illegal operands 'vmidt.q M300'

and then quits. Any ideas leading to a fix? I wasnt able to find any leads in the forums after browsing for an hour or so.

Post by **TyRaNiD** » Tue Jan 17, 2006 5:27 pm

You need to update your toolchain (specifically binutils) to make use of vfpu opcodes.

UsefulIdiot · Post by **UsefulIdiot** » Wed Jan 18, 2006 12:14 am

to what version specifically? apt says i have latest version of binutils and I would think the script would get the latest version it needs also

chp · Post by **chp** » Wed Jan 18, 2006 1:26 am

This is binutils for PSP we're talking about. Grab the latest toolchain-setup from [url]svn://svn.pspdev.org/psp/trunk/psptoolchain/[/url], rinse, repeat.

Panajev2001a · Post by **Panajev2001a** » Wed Jan 18, 2006 1:36 am

When will this be integrated in the standard oopo's psptoolchain script ?

Am I wrong or the current psptoolchain-20060110.tgz package when unpacked and run (./toolchain.sh) will not update binutils to the VFPU patched version ?

Post by **ooPo** » Wed Jan 18, 2006 1:49 am

If you read the included readme, you would have noticed the part where it tells you how to update to the very latest version of everything in the subversion repository.

I was waiting until the recent additions settled down before updating it on my site.

groepaz · Post by **groepaz** » Wed Jan 18, 2006 2:57 am

maybe another little script that first updates the toolchain script from svn, and then runs the toolchain script itself could be added....would be very useful (and avoid lots of simelar questions/problems) imho.

Panajev2001a · Post by **Panajev2001a** » Wed Jan 18, 2006 3:12 am

ooPo wrote:If you read the included readme, you would have noticed the part where it tells you how to update to the very latest version of everything in the subversion repository.

I was waiting until the recent additions settled down before updating it on my site.

ooPo, I can assure you I have learned the RTFM rule a LONG time ago :).

I am just wary of installing ANYTHING that is still in SVN trunk/daily snapshot that the maintainer has not deemed to put in the official/stable release changing the previous official/stable release in this case the psp toolchain script dated 2006-01-10.

I was waiting until the recent additions settled down before updating it on my site.

;).

I think I'll wait with you then: I trust your judgement :).

Panajev2001a · Post by **Panajev2001a** » Wed Jan 18, 2006 3:15 am

groepaz wrote:maybe another little script that first updates the toolchain script from svn, and then runs the toolchain script itself could be added....would be very useful (and avoid lots of simelar questions/problems) imho.

I guess it could help some, but my problem was not "how do I get the version currently in the SVN repository ?".
I phrased my post badly I think: a better question would have been "when will ooPo's release a new toolchain script and when will the new additions be moved out of the trunk and made available with simple execution of the toolchain script ?".

johnxmcmanus · Post by **johnxmcmanus** » Sat Jan 21, 2006 8:52 am

I think if you run "svn update" and hit enter from psptoolchain directory.

got this info from update article:
http://www.scriptscribbler.com/psp/tuto ... sson01.htm

Post by **ooPo** » Sat Jan 21, 2006 5:01 pm

groepaz wrote:maybe another little script that first updates the toolchain script from svn, and then runs the toolchain script itself could be added....would be very useful (and avoid lots of simelar questions/problems) imho.

This is why, as I've stated many times, the readme.txt mentions that you can just type 'svn update' to get the latest version automatically. There's no need for a wrapper script or other magery... a very simple command does it all.

Anyway, its moot now as I've modified the script (in the 20060120 release) to use 'svn cat' to grab the latest version of the patches each and every time it is run.

Perhaps someday when it all settles down I'll make it grab only a specific, known-stable revision number. I don't imagine that day will be anytime in the near future, however.

Enjoy.