This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I've successfully built cross-toolchains for i686-pc-linux-gnu using crosstool-0.42 on Cygwin and Mac OS X. I used demo-i686.sh, i686.dat, and gcc-4.1.0-glibc-2.3.6.dat. When running "file" on the test programs, i686-pc-linux-gnu-hello-static i686-pc-linux-gnu-hello i686-pc-linux-gnu-hello2-static i686-pc-linux-gnu-hello2, I get: $ file i686-pc-linux-gnu-hello* i686-pc-linux-gnu-hello: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.3, dynamically linked (uses shared libs), not stripped i686-pc-linux-gnu-hello-static: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.3, statically linked, not stripped i686-pc-linux-gnu-hello2: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.3, dynamically linked (uses shared libs), not stripped i686-pc-linux-gnu-hello2-static: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.3, statically linked, not stripped These programs run correctly on all GNU/Linux 2.6 systems I tested on. But is there a reason why the file program outputs "for GNU/Linux 2.4.3". For all other executables compiled natively on my GNU/Linux system, file program outputs "for GNU/Linux 2.6.9". Is there a reason for this? I'm using gcc-4.1.0-glibc-2.3.6.dat which has the following (Note the LINUX_DIR and LINUX_SANITIZED_HEADER_DIR are 2.6* and linux-2.6.15.4.tar.bz2 are downloaded and used): BINUTILS_DIR=binutils-2.16.1 GCC_CORE_DIR=gcc-3.3.6 GCC_DIR=gcc-4.1.0 GLIBC_DIR=glibc-2.3.6 LINUX_DIR=linux-2.6.15.4 LINUX_SANITIZED_HEADER_DIR=linux-libc-headers-2.6.12.0 GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.3.6 GDB_DIR=gdb-6.4 BINUTILS_EXTRA_CONFIG="--enable-64-bit-bfd --enable-shared --disable-werror" GCC_EXTRA_CONFIG="--disable-altivec --enable-nls --disable-werror --disable-libunwind-exceptions --enable-shared --enable-threads=posix --enable-__cxa_exit --enable-clocale=gnu" GLIBC_EXTRA_CONFIG="" GLIBC_EXTRA_ENV="" GLIBC_EXTRA_CC_ARGS="" EXTRA_TARGET_CFLAGS="" GLIBC_ADDON_OPTIONS="" The executables seem to run w/o any problem. So, if I were to use this cross-toolchain in distributed compilation (distcc) with the native-toolchain on my GNU/Linux system, can I expect correctly created binaries? (I have yet to try this out) I have the entire build log saved, but it is large. I can post it if it is needed. Thanks in advance. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |