glibc+sysenter sources..?
I found the binaries (ftp://people.redhat.com/drepper/glibc/2.3.1-25/) but the sources don't seem to be available. (That makes it hard to test, since my 2.5 system is running debian..)
Preferable would be a patch against the standard 2.3.1 (rather than one against the redhat sources) but I can probably detangle it if needed.
Also, has this been tested under SMP or am I forging new ground? (dual ppro 200 system under 2.5.66-bk10.)
Signature · 1 line
Disconnect <[email protected]>
Quoted 9 lines · Disconnect
I found the binaries (ftp://people.redhat.com/drepper/glibc/2.3.1-25/) but the sources don't seem to be available. (That makes it hard to test, since my 2.5 system is running debian..)
Preferable would be a patch against the standard 2.3.1 (rather than one against the redhat sources) but I can probably detangle it if needed.
Also, has this been tested under SMP or am I forging new ground? (dual ppro 200 system under 2.5.66-bk10.)
Just get a recent version of glibc. 2.3.2 includes the patches, I think. That'll be in Debian/unstable in another week or so I bet.
Signature · 2 lines
Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
Quoted 6 lines · Daniel Jacobowitz
Quoted 3 lines · Disconnect
I found the binaries (ftp://people.redhat.com/drepper/glibc/2.3.1-25/) but the sources don't seem to be available. (That makes it hard to test, since my 2.5 system is running debian..)
Just get a recent version of glibc. 2.3.2 includes the patches, I think. That'll be in Debian/unstable in another week or so I bet.
Probably, but I'm running testing (I like it to at least -mostly- work ;) ..) and still would prefer the 2.3.1 patches. (Among other things, its easier to test changes if you do them in small batches; a libc upgrade from 2.3.1 to 2.3.2 is hardly 'small'. And the 2.3.2 changelog doesn't mention sysenter specifically, although I haven't read it in detail to see if its mentioned obliquely.)
Since the binaries are being distributed there, I had expected to find sources in the same place.. or at least -somewhere-..
Signature · 1 line
Disconnect <[email protected]>
Quoted 15 lines · Disconnect
Quoted 6 lines · Daniel Jacobowitz
Quoted 3 lines · Disconnect
I found the binaries (ftp://people.redhat.com/drepper/glibc/2.3.1-25/) but the sources don't seem to be available. (That makes it hard to test, since my 2.5 system is running debian..)
Just get a recent version of glibc. 2.3.2 includes the patches, I think. That'll be in Debian/unstable in another week or so I bet.
Probably, but I'm running testing (I like it to at least -mostly- work ;) ..) and still would prefer the 2.3.1 patches. (Among other things, its easier to test changes if you do them in small batches; a libc upgrade from 2.3.1 to 2.3.2 is hardly 'small'. And the 2.3.2 changelog doesn't mention sysenter specifically, although I haven't read it in detail to see if its mentioned obliquely.)
Quoted 2 lines
Since the binaries are being distributed there, I had expected to find sources in the same place.. or at least -somewhere-..
Try here: ftp://ftp.gnu.org/gnu/glibc/
Steven
Quoted 9 lines · Steven Cole
Quoted 6 lines · Disconnect
Quoted 3 lines · Daniel Jacobowitz
Quoted 2 lines · Disconnect
I found the binaries (ftp://people.redhat.com/drepper/glibc/2.3.1-25/) but the sources don't seem to be available.
Since the binaries are being distributed there, I had expected to find sources in the same place.. or at least -somewhere-..
Try here: ftp://ftp.gnu.org/gnu/glibc/
That would be the sources to the original 2.3.1 or 2.3.2 (depending). That would -not- be the sources to ftp://people.redhat.com/drepper/glibc/2.3.1-25/*.rpm, which is a derivative version. Shall we play the GPL game? The bins were distribute to me (they're sitting on the machine in question) with no sources available.
C'mon people, enough with the obvious/troll/etc .. if you don't have the source or patches used to generate those bins (and you don't know where to get them) then its a safe bet that I'm not talking to you....
(And fwiw, I did find parts of them by spending a few hours curled up with the glibc cvs list archive, changelog, etc. But - as has been noted in the various B*K* flamewars - cvs does a really horrid job of changeset management.. its even more entertaining when you try to use cvsweb to extact them..)
Signature · 1 line
Disconnect <[email protected]>