When running sb2-init I'm getting the following output: [EMAIL PROTECTED]:~$ sb2-init arm /home/developer/sbox2/bin/cross_compiler/usr/bin/gcc Using /home/developer/sbox2/bin/cross_compiler/usr/bin/gcc to detect target architecture: Finished writing sb2.config checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i386-strip... no checking for strip... strip configure: WARNING: In the future, Autoconf will not detect cross-tools whose name does not start with the host triplet. If you think this configuration is useful to you, please write to [EMAIL PROTECTED] checking for i386-gcc... no checking for gcc... gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
Running /home/developer/sbox2/bin/scratchbox/bin/sb2-build-libtool failed You can run this manually later, otherwise your sb2 environment is correctly setup and ready to use [EMAIL PROTECTED]:~$ The error in config.log looks like this: ## ----------- ## ## Core tests. ## ## ----------- ## configure:2035: checking for a BSD-compatible install configure:2091: result: /usr/bin/install -c configure:2102: checking whether build environment is sane configure:2145: result: yes configure:2173: checking for a thread-safe mkdir -p configure:2212: result: /bin/mkdir -p configure:2225: checking for gawk configure:2241: found /usr/bin/gawk configure:2252: result: gawk configure:2263: checking whether make sets $(MAKE) configure:2284: result: yes configure:2364: checking for i386-strip configure:2394: result: no configure:2404: checking for strip configure:2420: found /usr/bin/strip configure:2431: result: strip configure:2445: WARNING: In the future, Autoconf will not detect cross-tools whose name does not start with the host triplet. If you think this configuration is useful to you, please write to [EMAIL PROTECTED] configure:2524: checking for i386-gcc configure:2554: result: no configure:2564: checking for gcc configure:2580: found /usr/bin/gcc configure:2591: result: gcc configure:2829: checking for C compiler version configure:2836: gcc --version >&5 ./configure: line 2837: /usr/bin/gcc: No such file or directory configure:2839: $? = 127 configure:2846: gcc -v >&5 ./configure: line 2847: /usr/bin/gcc: No such file or directory configure:2849: $? = 127 configure:2856: gcc -V >&5 ./configure: line 2857: /usr/bin/gcc: No such file or directory configure:2859: $? = 127 configure:2882: checking for C compiler default output file name configure:2909: gcc conftest.c >&5 ./configure: line 2910: /usr/bin/gcc: No such file or directory configure:2912: $? = 127 configure:2950: result: configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "libtool" | #define PACKAGE_TARNAME "libtool" | #define PACKAGE_VERSION "1.5.26" | #define PACKAGE_STRING "libtool 1.5.26" | #define PACKAGE_BUGREPORT "[EMAIL PROTECTED]" | #define PACKAGE "libtool" | #define VERSION "1.5.26" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:2957: error: C compiler cannot create executables See `config.log' for more details. Here is a little background on what I've gotten done so far. I'm currently working on an ARM system we want to run Debian on. I've gone through the steps of building a rootfs using debootstrap and created cross compilers using apt-cross and dpkg-cross to create deb packages. The steps I took can be found at http://www.emdebian.org/tools/crossdev.html I'm now at the stage of creating the Scratchbox environment. I've built both Scratchbox2 and Qemu from source following the steps posted at http://www.evidence.eu.com/component/option,com_mambowiki/Itemid,366/ My directory structure looks like this: $HOME/sbox2/ rootfs/ src/ bin/ qemu/ bin/ share/ scratchbox/ bin/ lib/ share/ cross_compiler/ usr/ bin/ (where gcc is located lib/ When I compile a binary outside of scratchbox it works just fine. [EMAIL PROTECTED]:~$ echo "main(){}" > dummy.c [EMAIL PROTECTED]:~$ $HOME/sbox2/bin/cross_compiler/usr/bin/gcc dummy.c [EMAIL PROTECTED]:~$ file a.out a.out: ELF 32-bit LSB executable, ARM, version 1, dynamically linked (uses shared libs), for GNU/Linux 2.6.12, not stripped [EMAIL PROTECTED]:~$ When I compile a binary inside of scratchbox I get the following error [SB2 simple arm] [EMAIL PROTECTED] ~ $ $HOME/sbox2/bin/cross_compiler/usr/bin/gcc dummy.c bash: /home/developer/sbox2/bin/cross_compiler/usr/bin/gcc: No such file or directory [SB2 simple arm] [EMAIL PROTECTED] ~ $ Has anyone seen this problem? I've been using the original Scratchbox for a few years now and would like to upgrade to the new version but so far I'm not having any luck. -- ------------------------------------------------------------------ Jeff Parent Computer Engineer
pgpEL5tmoJ5Xs.pgp
Description: PGP signature
_______________________________________________ Scratchbox-users mailing list Scratchbox-users@lists.scratchbox.org http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users