Help test the newtoolchain script.

harleyg · Post by **harleyg** » Wed Feb 15, 2006 4:27 am

Just because there new to something, you shouldn't dumb down things you say to them. It's a simple command and its the basics. If i didn't tell him, then he would always think you have to close it. I was only trying to help.
Sorry, ill keep my mouth shut in the future.

Post by **ooPo** » Wed Feb 15, 2006 5:29 am

There's a difference between 'dumbing down' and 'sticking to the basics'.

Your method did nothing to tell the user about how the .bashrc file is run when you start a new shell, a concept that is far more important to understand than an arcane command the user is being told to memorize.

The mind works with logical, intuitive concepts. Edit a startup script and you'll know it is run when you start. Edit a text file and execute it with some poorly-named 'source' command and you'll have him wondering if he has to do that each time he makes a change, or each time he logs in, or who knows what else he'll possibly think up.

harleyg · Post by **harleyg** » Wed Feb 15, 2006 6:16 am

It's pretty obvious though, but yes, i should of mentioned that.
When editing the ~/.bashrc file, if you cannot log out and in again, you should use source ~/.bashrc. Else, you should log out / in.
Sorry ooPo.

Paolo · Post by **Paolo** » Wed Feb 15, 2006 5:29 pm

ooPo wrote:When you added those lines to your .bashrc, did you quit and re-open the cygwin shell window before trying to run the toolchain script?

Adding stuff to your startup script only works if you restart.

Yes, I re-opened the shell.
This is strange, I had pspsdk up and running for a long time. Then I had some
troubles with Visual C++ IDE, which I had to re-install several times, and as a
side effect I wasn't able to build my PSP projects anymore.
I tried to reinstall pspsdk with the latest version of "traditional" toolchain script,
but it didn't work anymore, even if completely reinstalled cygwin etc.

Oh my, getting desperate here... :(

Post by **ooPo** » Thu Feb 16, 2006 1:36 am

Well, I'm stumped then...

There are some strange problems with the latest version of cygwin, but not being able to find psp-ar isn't one of them. That usually points to a path problem as it would have failed much earlier in the process if it couldn't build psp-ar during the binutils step.

Paolo · Post by **Paolo** » Thu Feb 16, 2006 6:52 pm

Is there anything I could add/modify in toolchain script in order to get some debugging data...?

Edit: Here's my ENV variables, could there be something in them?

!:: = ::\
!C: = C:\cygwin\bin
ALLUSERSPROFILE = C:\Documents and Settings\All Users
APPDATA = C:\Documents and Settings\Administrator\Application Data
CLASSPATH = C:\Program Files\Java\j2re1.4.2\lib\ext\QTJava.zip
COMMONPROGRAMFILES = C:\Program Files\Common Files
COMPUTERNAME = ASUKA
COMSPEC = C:\WINDOWS\system32\cmd.exe
CVS_RSH = /bin/ssh
DXSDK_DIR = C:\Program Files\Microsoft DirectX SDK (December 2005)\
FP_NO_HOST_CHECK = NO
HOME = /home/Administrator
HOMEDRIVE = C:
HOMEPATH = \Documents and Settings\Administrator
HOSTNAME = Asuka
INCLUDE = C:\Program Files\Common Files\SpeechEngines\Microsoft Visual Studio .NET\FrameworkSDK\include\;c:\Program Files\Common Files\SpeechEngines\Microsoft
INFOPATH = /usr/local/info:/usr/share/info:/usr/info:
LIB = C:\Program Files\MagicDraw\lib;
LOGONSERVER = \\ASUKA
MAKE_MODE = unix
MANPATH = /usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man
NUMBER_OF_PROCESSORS = 1
OLDPWD = /home/Administrator
OS = Windows_NT
PATH = /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:"C:/Program Files/Microsoft DirectX SDK (December 2005)/Utilities/Bin/x86":/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/ATI Technologies/ATI Control Panel:/cygdrive/c/Program Files/backburner 2/:/cygdrive/c/Program Files/Common Files/Adobe/AGL:/cygdrive/c/Program Files/QuickTime/QTSystem/:.: /winnt: c:/Program Files/Photoshop CS2/Presets/Tools: c:/Program Files/MagicDraw/bin: :/usr/local/pspdev/bin
PATHEXT = .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PKG_CONFIG_PATH = /usr/X11R6/lib/pkgconfig
PRINTER = HP Color LaserJet 4650 PS
PROCESSOR_ARCHITECTURE = x86
PROCESSOR_IDENTIFIER = x86 Family 6 Model 13 Stepping 6, GenuineIntel
PROCESSOR_LEVEL = 6
PROCESSOR_REVISION = 0d06
PROGRAMFILES = C:\Program Files
PROMPT = $P$G
PS1 = \[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$
PSPDEV = /usr/local/pspdev
PWD = /home/Administrator/newtoolchain
QMAKESPEC = /usr/lib/qt3/mkspecs/cygwin-g++
QTDIR = /usr/lib/qt3
QTJAVA = C:\Program Files\Java\j2re1.4.2\lib\ext\QTJava.zip
SESSIONNAME = Console
SHLVL = 1
SYSTEMDRIVE = C:
SYSTEMROOT = C:\WINDOWS
TEMP = /cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp
TERM = cygwin
TMP = /cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp
USER = Administrator
USERDOMAIN = ASUKA
USERNAME = Administrator
USERPROFILE = C:\Documents and Settings\Administrator
VS71COMNTOOLS = C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\
WINDIR = C:\WINDOWS
_ = ./toolchain.pl

Post by **ooPo** » Fri Feb 17, 2006 1:13 am

If you're running the newtoolchain script, it logs everything to logfile.txt.

Paolo · Post by **Paolo** » Tue Feb 21, 2006 8:22 pm

Ok, solved. Apparently DirectX SDK caused the problem. After uninstalling
the dx sdk, and manually removing some leftover garbage from enviroment
variables, I finally managed to run the toolchain script succesfully! :)

It only took 12 re-installations of cygwin and something like 20 attempts to
run the toolchain script! LOL! Lesson; check your paths, and then re-check them...

New toolchain script is really really sweet! Thanks! :)

Post by **ooPo** » Wed Feb 22, 2006 12:43 am

I'm happy it is finally working for you. Perhaps this will help others who are having similar problems.