On Wed, Mar 12, 2014 at 04:53:20PM +0200, Kai Ruottu wrote: > You can spy how the current GCC was configured via 'gcc -v'. I > could guess a 'mipsel-linux-gnu' or > 'mipsel-linux-gnueabi' being used in its configure command. Or > things to define the default output > and CPU to be a 32-bit one instead of the expected 64-bit.... Here's the output of my "gcc -v": Using built-in specs. Target: mipsel-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.4.5-8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.4 --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --disable-libssp --enable-targets=all --enable-checking=release --build=mipsel-linux-gnu --host=mipsel-linux-gnu --target=mipsel-linux-gnu Thread model: posix gcc version 4.4.5 (Debian 4.4.5-8) > Just for curiosity I checked what the 'gcc-4.3_4.3.5-4_mipsel.deb' > package from 2012 (like your > system) was and saw it being configured using all the three system > names being the same : > > --build=mipsel-linux-gnu --host=mipsel-linux-gnu > --target=mipsel-linux-gnu > > (using 'strings gcc-4.3 | less' and searching for 'configure') You > should check also the other options > used with the existing native GCC whether they could be needed... My package version is actually slightly different than that, but your observation is correct. Unfortunately, I don't really know what that means in context. Is there something wrong with this configuration? Nothing seems to really jump out at me. If so, what can I do to fix it? -- Harry Prevor
