Why in the world did they use 2.1.3 since it is not installed (AFAIK) on any
distributed
system ?
This race for the latest glibc is puzzling me. Since glibc is at the base of
everything,
binary distribs should use the most commonly used so people could use them !
For the adventurous ones (on the bleeding glibc edge) , as said below, there should not
be any trouble using the source.
I don't mind compiling. Just getting fed up setting up the xc source tree each time.
I am worried about this new glibc.
When you are distributing your own software to other people with "old" (means 3 month
old !)
distrib and you cannot compile for their system because their glibc is too old (or
yours too new ???),
things tends to get quite complicated !
Now I have to use vmware for running linux in a linux box : redhat 4.2 for libc5,
redhat 5.2 for 2.0,
redhat 6.1 for 2.1 !!!
Ok I could setup a cross-compiling environnement. I don't find this THAT simple. What
about redhat doing
it for us if they are to change glibc so often ?
Philippe
"Martin A. Marques" <[EMAIL PROTECTED]> writes:
> On Sat, 05 Feb 2000, Wayne Dyer wrote:
> > Bernhard Rosenkraenzer wrote:
> > > On Fri, 4 Feb 2000, Philippe Moutarlier wrote:
> > >
> > > > I cannot find any . Does anybody have a reference ?
> > >
> > > ftp://rawhide.redhat.com/pub/rawhide/
> >
> > Careful out there. The RPMs there were built with (and require) glibc 2.1.3
>
> Use the source Luke, use the source.... :-)))
>
>
> --
> "And I'm happy, because you make me feel good, about me." - Melvin Udall
> -----------------------------------------------------------------
> Martín Marqués email: [EMAIL PROTECTED]
> Santa Fe - Argentina http://math.unl.edu.ar/~martin/
> Administrador de sistemas en math.unl.edu.ar
> -----------------------------------------------------------------
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
