Problems with Cygwin Cross-Compiler

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
FBSC
Posts: 6
Joined: Tue Jan 12, 2010 6:34 am

Problems with Cygwin Cross-Compiler

Post by FBSC »

Hello, today i tried to create a Cygwin cross-compiler following the instructions on GCC Cross-Compiler.
I downloaded binutils and put it in /usr/src/binutils-2.9.1, ran all the cmds on the wiki, but at:

Code: Select all

cd /usr/src/build-binutils
../binutils-2.9.1/configure --target=$TARGET --prefix=$PREFIX --disable-nls
make all <--
gave me an error:

Code: Select all

make[1]: Entering directory `/usr/src/build-binutils/libiberty'
if [ -n "" ] && [ ! -d pic ]; then \
          mkdir pic; \
        else true; fi
touch stamp-picdir
echo "# !Automatically generated from ../../binutils-2.9.1/libiberty/functions.d
ef"\
          "- DO NOT EDIT!" >needed2.awk
grep '^DEFVAR(' < ../../binutils-2.9.1/libiberty/functions.def \
         | sed -e '/DEFVAR/s|DEFVAR.\([^,]*\).*|/\1/ { printf "#ifndef NEED_\1\\
n#define NEED_\1\\n#endif\\n" }|' \
         >>needed2.awk
grep '^DEFFUNC(' < ../../binutils-2.9.1/libiberty/functions.def \
         | sed -e '/DEFFUNC/s|DEFFUNC.\([^,]*\).*|/\1/ { printf "#ifndef NEED_\1
\\n#define NEED_\1\\n#endif\\n" }|' \
         >>needed2.awk
gcc -c -g -O2 -I. -I../../binutils-2.9.1/libiberty/../include -DNEED_sys_siglist
 -DNEED_basename -DNEED_strsignal ../../binutils-2.9.1/libiberty/dummy.c 2>/dev/
null
make[1]: *** [dummy.o] Error 1
make[1]: Leaving directory `/usr/src/build-binutils/libiberty'
make: *** [all-libiberty] Error 2

How can i solve this? I use Windows XP SP3, if can help
User avatar
Solar
Member
Member
Posts: 7615
Joined: Thu Nov 16, 2006 12:01 pm
Location: Germany
Contact:

Re: Problems with Cygwin Cross-Compiler

Post by Solar »

To quote from the tutorial:
Note: The versioning scheme used is that each fullstop separates a full number, eg. 2.8.0 2.9.0 2.10.0 2.11.0, this may be confusing if you're used to Windows' program's schemes (eg. 1.01 1.02 etc).
Binutils 2.9 is ancient. The current version is 2.20, which the table Cross-Compiler_Successful_Builds would have told you.

Nevermind. Happens rather frequently. :wink:

PS: And because it does, I changed the wording a bit:
Note: The versioning scheme used is that each fullstop separates a full number, i.e. binutils 2.20.0 is newer than 2.9.0. This may be confusing, if you have not encountered this (quite common) versioning scheme yet, when looking at an alphanumerically sorted list of tarballs: The file at the bottom of the list is not the latest version!
Every good solution is obvious once you've found it.
FBSC
Posts: 6
Joined: Tue Jan 12, 2010 6:34 am

Re: Problems with Cygwin Cross-Compiler

Post by FBSC »

Thanks, seems to be "making"... When it will be finished 'll try and compile gcc
Post Reply