| View previous topic :: View next topic |
| Author |
Message |
J.F.
Joined: 22 Feb 2004
Posts: 2906
|
 Posted: Mon Nov 13, 2006 9:26 am Post subject: Trouble building toolchain |
 |
|
I recently built a new system and I am in the process of setting up the psp and ps2 toolchains. The psp toolchain went fine, but building the ps2 toolchain gives this error:
| Code: | configure: error: Unrecognized target system type; please check config.sub.
gmake: *** [configure-opcodes] Error 1
ERROR BUILDING BINUTILS (binutils-2.14 ee) |
I've tried this with the default 4.1 gcc, 3.4 gcc, and 3.3 gcc. All give the exact same error. |
|
| Back to top |
|
 |
Chewi
Joined: 26 Nov 2006
Posts: 109
Location: Perth, Scotland
|
| Posted: Tue Nov 28, 2006 12:13 pm Post subject: |
|
|
| What target did you choose? |
|
| Back to top |
|
|
J.F.
Joined: 22 Feb 2004
Posts: 2906
|
| Posted: Wed Nov 29, 2006 8:30 am Post subject: |
|
|
| This is the toolchain script... all you do is type "./toolchain.sh" and it handles everything from downloading the correct gcc/binutils/newlib to patching to compiling ps2sdk. At least, it USED to. :) |
|
| Back to top |
|
|
J.F.
Joined: 22 Feb 2004
Posts: 2906
|
| Posted: Sat Dec 02, 2006 9:51 am Post subject: |
|
|
Still getting that error. Here's more of the output:
| Code: | Configuring in opcodes
loading cache .././config.cache
checking for Cygwin environment... no
checking for mingw32 environment... no
checking host system type... x86_64-unknown-linux-gnu
checking target system type... Invalid configuration `ee': machine `ee' not recognized
checking build system type... x86_64-unknown-linux-gnu
checking for gcc... (cached) gcc
checking whether the C compiler (gcc -g -O2 ) works... yes
checking whether the C compiler (gcc -g -O2 ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for POSIXized ISC... no
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for ar... (cached) ar
checking for ranlib... (cached) ranlib
checking for ld used by GCC... ld
checking if the linker (ld) is GNU ld... yes
checking for ld option to reload object files... -r
checking for BSD-compatible nm... nm
checking whether ln -s works... yes
checking how to recognise dependant libraries... file_magic ELF [0-9][0-9]*-bit [LM]SB (shared object|dynamic lib )
checking for object suffix... o
checking for executable suffix... no
checking for file... /usr/bin/file
checking for ranlib... (cached) ranlib
checking for strip... strip
updating cache .././config.cache
loading cache .././config.cache within ltconfig
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
finding the maximum length of command line arguments... 49153
checking if gcc supports -c -o file.o... yes
checking if gcc supports -fno-rtti -fno-exceptions ... no
checking whether the linker (ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking command to parse nm output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
creating libtool
updating cache .././config.cache
loading cache .././config.cache
configure: error: Unrecognized target system type; please check config.sub.
gmake: *** [configure-opcodes] Error 1
ERROR BUILDING BINUTILS (binutils-2.14 ee)
|
|
|
| Back to top |
|
|
J.F.
Joined: 22 Feb 2004
Posts: 2906
|
| Posted: Sat Dec 02, 2006 10:35 am Post subject: |
|
|
Okay - I figured that problem out... I don't run toolchain.sh in the toolchain directory, so as a result, it couldn't find the patches. Rather than complain and error out, it keeps happily trying to build the stuff. :)
The PSP toolchain didn't have a problem because it always fetches the latest patches from svn. The PS2 toolchain should probably do the same.
EDIT: Also, don't forget (like I did) that the ee gcc won't compile with gcc 4.x. If you're running something like Fedora Core 6 (like I am), go into the repo and install gcc-3.4, then run the toolchain like this:
| Code: | | CC=gcc34 ./toolchain.sh |
|
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
