uclibc configuration

[Carl Miller]

On Mon, Apr 19, 2004 at 09:57:51AM -0700, Daniel Kegel wrote:
> Mark Beckwith wrote:
> >Hi, I've built crosstool for the arm using the supplied .dat file for v. 
> >0.27: gcc-2.95.3-glibc-2.1.3.dat.  This is working great.
> >
> >Now I'd like to use uClibc 0.9.26 with the same compiler.   I'm a little 
> >confused
> >with the dat file settings.  Do I just set GLIBC_DIR to be uclibc-0.9.26?
> >What do I do with the GLIBCTHREADS_FILENAME and GLIBCCRYPT_FILENAME 
> >settings?  
> >BINUTILS_DIR=binutils-2.11.2
> >BINUTILS_URL=ftp://ftp.gnu.org/pub/gnu/binutils
> >GCC_DIR=gcc-2.95.3
> >GLIBC_DIR=uclibc-0.9.26
> >LINUX_DIR=linux-2.4.21
> >GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.1.3
> >GLIBCCRYPT_FILENAME=glibc-crypt-2.1
> 
> Heh.  Have a look at
> http://sources.redhat.com/ml/crossgcc/2003-12/msg00144.html
> I think he's working up a new set of patches that are less
> invasive, though...

Yep.  I'm in the chaos of my last week at this employer, and my final
task is to make a nice crosstool-based uClibc toolchain build system.
I'm at the point where I could give you some pre-alpha quality patches
that would be under heavy development, but might be good enough to work.
Or you could wait a few days until I make a more formal release that I
have some confidence in.

I'd definitely recommend using newer versions of gcc and binutils,
however.  Both of those listed are quite old.  My previous set of
patches were for binutils 2.14.90.0.5 and gcc 3.3.2.  The upcoming
set will be for binutils 2.14.90.0.5 or 2.14 release, and gcc 3.3.3.
I won't be spending any effort backporting them to earlier tool
versions, but if that's important to you, feel free to do so yourself.

Also, I'm currently using uClibc 0.9.23, and that will be the version
first supported by my new set of patches, but I hope to quickly follow
on with support for 0.9.26.


If you absolutely can't wait, and you're not confident in negotiating
the choppy waters of using under-development pre-alpha software, give my
old set of patches a try, and just use the .dat file included in them
verbatim.  They had a couple minor gotchas, which I can talk you
through, but in the end worked out alright.  In addition to the message
from the mailing list archives referenced above by Dan, see these:

http://sources.redhat.com/ml/crossgcc/2003-12/msg00168.html
http://sources.redhat.com/ml/crossgcc/2004-01/msg00003.html

Good luck!  Hopefully I'll have something much better for you in about
a week...


                          -----Carl


                          

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com