[uClibc] Need help with compiling programs using uclibc in alternate location

Josh Goebel josh at dwgsolutions.com
Tue Dec 2 19:30:15 UTC 2003


What am I doing wrong?  This is in the middle of a make in the buildroot
directory that I downloaded from CVS.

make[4]: Entering directory
`/home/jgoebel/floppy/buildroot/toolchain_build_i386/binutils-build/bfd/
po'
file=/home/jgoebel/floppy/buildroot/toolchain_build_i386/binutils-2.14.9
0.0.6/bfd/po/`echo fr | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH no -o $file
/home/jgoebel/floppy/buildroot/toolchain_build_i386/binutils-2.14.90.0.6
/bfd/po/fr.po
/bin/sh: no: command not found
make[4]: *** [fr.gmo] Error 127
make[4]: Leaving directory
`/home/jgoebel/floppy/buildroot/toolchain_build_i386/binutils-build/bfd/
po'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/home/jgoebel/floppy/buildroot/toolchain_build_i386/binutils-build/bfd'
make[2]: *** [all-recursive-am] Error 2
make[2]: Leaving directory
`/home/jgoebel/floppy/buildroot/toolchain_build_i386/binutils-build/bfd'
make[1]: *** [all-bfd] Error 2
make[1]: Leaving directory
`/home/jgoebel/floppy/buildroot/toolchain_build_i386/binutils-build'
make: ***
[/home/jgoebel/floppy/buildroot/toolchain_build_i386/binutils-build/binu
tils/objdump] Error 2

Thanks,
Josh

-----Original Message-----
From: Manuel Novoa III [mailto:mjn3 at codepoet.org] 
Sent: Tuesday, December 02, 2003 11:31 AM
To: Josh Goebel
Cc: uclibc at uclibc.org
Subject: Re: [uClibc] Need help with compiling programs using uclibc in
alternate location

Hello,

On Tue, Dec 02, 2003 at 11:21:58AM -0500, Josh Goebel wrote:
> Forgive me, but with what I'm doing [building a floppy distro with
> BusyBox and uclibc compiled against Linux 2.0] is it possible to use
the
> pre-built development system for the i386 or must I build one from
> scratch with buildroot?

The pre-built rootfs images are built with the 2.4 kernel headers.
If you want to use 2.0, you will have to run buildroot yourself.

> Also, are the development environments themselves specific to how
uclibc
> is compiled?  The kernel I'm going to use the headers from could still
> change as well as the uclibc options... must all this be known
upfront?

Some uClibc config options change the ABI.  So you may need to
rebuild for some changes.

Manuel




More information about the uClibc mailing list