can someone explain the new layout of glibc tarballs?
Fri Oct 28 03:39:00 GMT 2005
Robert P. J. Day wrote:
> is there somewhere a good explanation of the contents of the
> leading edge glibc and related snapshot tarballs? here's what i've
> -rw-r--r-- 1 rpjday rpjday 15429830 Oct 27 21:10 glibc-20051024.tar.bz2
> -rw-r--r-- 1 rpjday rpjday 14541570 Oct 27 21:13 glibc-2.3-20051024.tar.bz2
> -rw-r--r-- 1 rpjday rpjday 151545 Oct 27 20:59 glibc-2.3-ports-20051024.tar.bz2
> -rw-r--r-- 1 rpjday rpjday 459553 Oct 27 21:00 glibc-ports-20051024.tar.bz2
> so, ignoring the standard glibc-2.3.5 release, what's going on in the
> above? the two glibc snapshots are *almost* the same size. the two
> ports snapshots are significantly different in size.
My guess is that the 2.3...20051024 ones are snapshots of the 2.3
branch (on the way to some possible future 2.3.6),
and the ones without 2.3 on them are snapshots of
the 2.4 branch (on the way to some future 2.4.0).
> how do the above relate to what you'd use to try to build a toolchain?
> a pointer to a URL would suit me just fine.
I haven't tried it, but all the glibc addons are probably similar;
you unpack the main glibc tarball, then cd into it and
unpack the addon. And that's your source tree.
See how my getandpatch.sh treated glibc-linuxthreads-$version.tar.gz,
and treat glibc-ports-$version similarly.
That's my guess, anyway.
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to firstname.lastname@example.org
More information about the crossgcc