Well, that's fantastic... Looks like I'm out, because I have no idea how to proceed with a Scratchbox blank filesystem, and building an i486/mips/ppc cross-compile environment fails. I was able to buid an ARM environment, but i486/mips/ppc builds fail no matter how I go about it:
------------------------------------------------------------------------------------------------ /usr/src/binutils-i486-linux-2.15 $ debuild -uc -us dpkg-buildpackage: source package is binutils-i486-linux dpkg-buildpackage: source version is 2.15-5 dpkg-buildpackage: source maintainer is <[EMAIL PROTECTED]> dpkg-buildpackage: host architecture is i386 fakeroot debian/rules clean dh_testdir dh_testroot mv debian .save.debian rm -rf * mv .save.debian debian # Add here commands to clean up after the build process. #-/usr/bin/make clean dh_clean dpkg-source -b binutils-i486-linux-2.15 dpkg-source: building binutils-i486-linux in binutils-i486-linux_2.15-5.tar.gz dpkg-source: building binutils-i486-linux in binutils-i486-linux_2.15-5.dsc debian/rules build tar xjf /usr/src/toolchain/binutils.tar.bz2 mv binutils*/* . ln -s . src mkdir build touch unpack-stamp dh_testdir # Add here commands to configure the package. cd build && env CC="gcc" ../src/configure --prefix=/usr --libdir=/usr/i486-linux/lib --build=i386-linux --host=i386-linux --disable-static --target=i486-linux creating cache ./config.cache checking host system type... i386-pc-linux-gnu checking target system type... i486-pc-linux-gnu checking build system type... i386-pc-linux-gnu checking for a BSD compatible install... /usr/bin/install -c gcc: installation problem, cannot exec `cc1': No such file or directory gcc: installation problem, cannot exec `cc1': No such file or directory *** The command 'gcc -o conftest -g conftest.c' failed. *** You must set the environment variable CC to a working compiler. make: *** [configure-stamp] Error 1 debuild: fatal error at line 764: dpkg-buildpackage failed! /usr/src/binutils-i486-linux-2.15 $ ------------------------------------------------------------------------------------------------ No, setting CC=/usr/lib/gcc/i486-linux/3.4.4/cc1 does not work. I don't even know whether this would get me to an EmDebian filesystem. I guess this project is just not ready. Carl Cook On Saturday 29 January 2005 14:07, Bernhard Fischer wrote: > On Sat, Jan 29, 2005 at 11:03:27AM -0800, Allen Curtis wrote: > >>>>chroot for de the devopment env or a chroot for the target > >>>>filesystem? > >>>>In the last case, you can only do this if the target is not another > >>>>architecture and I guess this is only a minority of the cases. > >> > >>Maybe the wiki should add a link to tldp's cross-compilation HOWTO? > >> > >The idea of a Wiki is that people can add content that they feel is > >useful. As people bring up Emdebian we should construct a howto > >section. Community involvement is good, even in documentation. > >(especially since I hate to do paperwork) > > (/me too ;) > I cannot find the cross-compile howto anymore, but anyway. Please feel > free to add this to the wiki (i won't do it). > > > A cross-compiler can be used to build binaries for an architecture other > than the compile-hosts arch. For [[http://gcc.gnu.org][GCC]] there is > [[http://kegel.com/crosstool/][crosstool]] which can be used to > bootstrap your cross-compiler. > > add short description on bootstrapping a cross-chain manually here > (binutils, gcc, a libc). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
