Re: [Ltib] "can't open gcc"

[Peter Barada]

On Thu, 2008-05-08 at 11:48 +0100, Stuart Hughes wrote:
> Hi Peter,
> 
> It's hard to tell what's happening here, but probably the best thing to
> do to track this down is to insert the following into
> dist/lfs-5.1/kernel/kernel-common.tmpl
> 
> $ cvs diff -u dist/lfs-5.1/kernel/kernel-common.tmpl
> Index: dist/lfs-5.1/kernel/kernel-common.tmpl
> ===================================================================
> RCS file: /sources/ltib/ltib/dist/lfs-5.1/kernel/kernel-common.tmpl,v
> retrieving revision 1.4
> diff -u -u -r1.4 kernel-common.tmpl
> --- dist/lfs-5.1/kernel/kernel-common.tmpl      4 Apr 2008 15:48:12 -0000     
>  1.4
> +++ dist/lfs-5.1/kernel/kernel-common.tmpl      8 May 2008 10:47:50 -0000
> @@ -92,6 +92,7 @@
>  then
>      make ARCH=$LINTARCH CROSS_COMPILE= HOSTCC="$BUILDCC" menuconfig
>  else
> +/bin/sh
>      yes "" | make ARCH=$LINTARCH CROSS_COMPILE= HOSTCC="$BUILDCC" oldconfig
>  fi
>  if [ -f $PLATFORM_PATH/${PKG_KERNEL_PRECONFIG} ]
> 
> 
> And then run: ./ltib -p kernel
> You will then get dropped to the shell prompt in the exact environment
> that the kernel gets built in.  From there you can do `which gcc` etc.
> For example on mine:
> 
> sh-3.00$ which gcc
> /opt/ltib/usr/spoof/gcc
> sh-3.00$ gcc -v
> Using built-in specs.
> Target: arm-none-linux-gnueabi
> Configured
> with: /usr/src/redhat/BUILD/cross-mlib/source/gcc-4.1.2/configure
> --target=arm-none-linux-gnueabi --host=i686-host_pc-linux-gnu
> --prefix=/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi
>  
> --with-sysroot=/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/arm-none-linux-gnueabi/sysroot
>  --enable-threads --enable-shared --disable-libssp --disable-libgomp 
> --disable-libmudflap --enable-languages=c,c++ --enable-__cxa_atexit 
> --disable-nls
> Thread model: posix
> gcc version 4.1.2
> 
> $ echo $TOOLCHAIN
> tc-fsl-x86lnx-armeabi-nptl-4.1.2-3.i386.rpm
> $ echo $TOOLCHAIN_CFLAGS
> -O2 -fsigned-char -mfloat-abi=i=softfp -mfpu=vfp
> $ echo $TOOLCHAIN_PREFIX
> arm-none-linux-gnueabi-
> $ echo $TOOLCHAIN_PATH
> /opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi
> 
> Also note that to see what the spoofer is actually calling, set:
> export FS_DEBUG=1
> 
> Regards, Stuart

Ubuntu uses 'dash', not 'bash' for /bin/sh...
The fix (Google is my friend) is:

sudo apt-get remove dash
sudo apt-get install bash


> On Wed, 2008-05-07 at 13:05 -0400, Peter Barada wrote:
> > I've produced a release .iso if the imx31lite work I've been doing and
> > installing/testing it on a different machine (Ubuntu usermode virtural
> > server).
> > 
> > I've done this with previous images successfully.  With my new image
> > building fails on the first invocation of the spoofed gcc with "can't
> > open gcc", but if I try to run the spoofed gcc from a shell started with
> > "./ltib -m shell", it succeeds.
> > 
> > Attached is the log of building the kernel where its Makefile was
> > replaced with one that only has:
> > 
> > oldconfig:
> >     set; which gcc; gcc -v
> > 
> > to dump the environment and then attempt to invoke the spoofed gcc
> > (which fails).
> > 
> > I've tried removing and reinstalling the LTIB .iso from scratch twice
> > now to no effect.
> > 
> > Any ideas why the "can't open gcc" message shows up?
> > 
> > Thanks in advance!
> > 
> 
> 
> 
> 
> _______________________________________________
> LTIB home page: http://bitshrine.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib