|
From: Torsten M. <tmohr@s.netic.de> - 2005-08-30 22:54:03
|
Hi, > cross compiler from where to where, i.e. which is your host > and what is target ? sorry for leaving out these informations. I use MinGW on Windows 2000, i want to generate a cross compiler that runs on Windows 2000 for an embedded controller, the NEC V850E. I successfully did this on a linux host and under cygwin. Basically i always configured and compiled binutils for that target. On MinGW i did this by: ../binutils-2.16/configure --target=v850e-unknown-elf make make install > Or in other words: > You may want to give a few more details as to what you are > trying to achieve and of course what your environment is etc. For gcc i did: ../gcc-3.4.4/configure --target=v850e-unknown-elf --enable-languages="c" > You are aware that you need a couple of system libs and headers > from the target system to successfully create your cross compiler ? Yes, i know that. I plan to install newlib-1.13.0 after installing gcc. > The errormsgs you posted _could_ result from using the wrong > set of headers but that's only a wild guess as I have no idea > what you are actually doing. I'd wonder, at that level i only want to build the gcc cross compiler for V850E, i'll install the libs later. I think that the problem is rather caused by some calls in gcc that are not available on MinGW. I thought there might be a patch available to work around these calls or to remove them where possible? Best regards, Torsten. |