Thanks for the information. I have always some problems. When I try to compile the gmp, mpc and mpfr dependanties of gcc I have to compile they for arm (CROSS_COMPILE) or for x86? Only the gcc compiler command have the options --build=i686 --host=arm-unknown-linux-gnueabi --target=arm-unknown-linux-gnueabi? Thanks Il giorno mar, 08/06/2010 alle 12.15 +0300, Kai Ruottu ha scritto: > 8.6.2010 10:25, Alessandro Biasci kirjoitti: > > > The host (where I compile the gcc) have 3GB of memory and the target > > (the ARM platform) have 32MB of memory. > > > > --build=arm-unknown-linux-gnueabi --host=arm-unknown-linux-gnueabi > > --target=arm-unknown-linux-gnueabi --srcdir=../.././libgcc > > --disable-intermodule --enable-checking=yes,types --disable-coverage > > --enable-languages=c > > > > ## --------- ## > > ## Platform. ## > > ## --------- ## > > > > hostname = icaro > > uname -m = arm > > uname -r = 2.6.32-22-generic > > uname -s = Linux > > uname -v = #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 > > > > They have the space for allocate a page in virtual memory. > > Something in the previous given data doesn't sound sane... > > > Maybe I insert some bad parameters for configure/compile the source > > code. > > A "normal" case would be when one produces a native GCC using : > > --build=i686-pc-linux-gnu --host=arm-unknown-linux-gnueabi > --target=arm-unknown-linux-gnueabi > > ie producing it on a Linux/x86 host using a 'arm-unknown-linux-gnueabi' > targeted crosscompiler to produce the resulting GCC binaries (xgcc, > cpp, cc1, collect2). This is the "Canadian Cross" case although here > $host = $target. More typical Canadian Cross case could be : > > --build=i686-pc-linux-gnu --host=i686-mingw32 > --target=arm-unknown-linux-gnueabi > > where $build != $host != $target > > So my guess is that you told '--build=arm-unknown-linux-gnueabi' which > isn't true at all ! >
