On Tue, Oct 01, 2002 at 04:25:21PM -0700, Russ Dill wrote:
I just uploaded a set of binary snapshots built from the CVS head
using RedHat's compat-gcc-7.3-2.96.110 package (which produces
code compatible with the gcc bundled with the RedHat 7.3 and is
the same which was producing
On Mit, 2002-10-02 at 11:13, José Fonseca wrote:
On Tue, Oct 01, 2002 at 04:25:21PM -0700, Russ Dill wrote:
I just uploaded a set of binary snapshots built from the CVS head
using RedHat's compat-gcc-7.3-2.96.110 package (which produces
code compatible with the gcc bundled with the
Title: RE: [Dri-devel] Re: Ann: gcc-2.96 compiled snapshots available (I'm going to smack redhat)
Its c code, so I don't think the version of gcc is that
important, what
matters is the GLIBC_2.3 symbol, it doesn't show up in the X driver,
because it isn't linked against libc, however
On Wed, Oct 02, 2002 at 01:15:26PM +0200, Michel Dänzer wrote:
You don't need to build for every system, just against an older version
of glibc.
I am not using these binary snapshots, but I appreciate this work. But
please do not compile it against RedHat's glibc2.3 version. RedHat is
the
On Wed, Oct 02, 2002 at 01:35:50PM +0200, Michael Thaler wrote:
On Wed, Oct 02, 2002 at 01:15:26PM +0200, Michel Dänzer wrote:
You don't need to build for every system, just against an older version
of glibc.
I am not using these binary snapshots, but I appreciate this work. But
please do not
On Wed, Oct 02, 2002 at 02:25:40PM +0100, Alan Cox wrote:
Get a clue.
glibc 2.3 is used because its newer, because it fixes lots of bugs,
because its more standards compliant, because it uses new syscalls.
Everyone will be using it soon enough.
glibc 2.3 is LSB compliant, like current
On Wed, Oct 02, 2002 at 10:33:11AM -0700, Russ Dill wrote:
[...]
But I see rough times ahead for the binary snapshots. I surely can't make
one for each system out there. And if the others distros don't also
upgrade to glic-2.3 then I think the best is to completely stop the
snapshots builds
*please* find a machine with a copy of glibc2.2, wait until glibc2.3
actually becomes a release to compile against it (or, if in the case of
redhat, distribute it with your distro)
The final RHL 8.0 was released 2 days ago. I'll upgrade soon but I
already checked and it has the same
release version, and using that. CVS versions of software often contain
new bugs and even security vulnerabilities, it is far more prudent to
work with a release version of such a major system component. Because of
this, most distros will probably wait until it becomes a release until
they
