--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Save Money, Buy GENERIC!
Prescription drugs with NO prior prescription needed!
- XANAX - (to treat anxiety)
- PHENTERMINE - (for weight loss)
- Viagra - (got wood?)
- Ambian - (For a Great Nights Sleep)
- Lipitor - (to reduce cholesterol)
- NEXIUM - (to treat acid reflux and GERD)
- PAXIL
Richard Henderson <[EMAIL PROTECTED]> writes:
> Because of that, I was thinking that perhaps it might be best to
> just increment the soname to libc.so.6.2.
> [...]
>
> Cc'ed to debian-glibc, since they're the only currently viable alpha
> distribution that I'm aware of. I see yall are still usi
Processing commands for [EMAIL PROTECTED]:
> reassign 237033 lxdoom
Bug#237033: errno not exported with GLIBC_2.0 version
Bug reassigned from package `libc6' to `lxdoom'.
> retitle 237033 please recompile with proper errno.h and recent libc6
Bug#237033: errno not exported with GLIBC_2.0 version
C
Check the MD5 before prelinking, prelink the binary and then check it
again with prelink -y --md5. If both md5 outputs are different, it means
that prelink did change the binary. It should not since prelink
processes that kind of symbols (called "conflicts" on prelink language),
on a special way an
On mar, 2004-03-09 at 18:07, Andrés Roldán wrote:
> Check the MD5 before prelinking, prelink the binary and then check it
> again with prelink -y --md5. If both md5 outputs are different, it means
> that prelink did change the binary. It should not since prelink
> processes that kind of symbols (ca
On Tue, Mar 09, 2004 at 05:21:57PM +0100, Laurent Bonnaud wrote:
> > It works here, and correctly binds to the old libc.so.6 in /lib. There
> > is code in ld.so to handle this exact case, and I can't see any reason
> > it would work on my system but not on yours.
>
> I'm using prelink. Does it m
On Tue, Mar 09, 2004 at 05:21:57PM +0100, Laurent Bonnaud wrote:
> > It works here, and correctly binds to the old libc.so.6 in /lib. There
> > is code in ld.so to handle this exact case, and I can't see any reason
> > it would work on my system but not on yours.
>
> I'm using prelink. Does it m
On Tue, Mar 09, 2004 at 05:28:24PM +0100, Laurent Bonnaud wrote:
> > It shouldn't, since the prelinking failed, but maybe it does. Try
> > unprelinking just the lxdoom binary.
>
> It works:
>
> # prelink -u /usr/games/lxdoom
> # prelink -u /usr/games/lxdoom-game-server
> $ debsums -s lxdoom
> [O
On Tue, Mar 09, 2004 at 05:07:46PM +0100, Laurent Bonnaud wrote:
> > Output of LD_DEBUG=all lxdoom, please?
>
> Here it is.
It works here, and correctly binds to the old libc.so.6 in /lib. There
is code in ld.so to handle this exact case, and I can't see any reason
it would work on my system but
> README.Debian.gz says "The application should continue to run for now" wrt
> using errno, but this clearly isn't the case in lxdoom's case.
It would be a good idea to recompile lxdoom with proper
#include
directives anyway.
--
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/
> It works here, and correctly binds to the old libc.so.6 in /lib. There
> is code in ld.so to handle this exact case, and I can't see any reason
> it would work on my system but not on yours.
I'm using prelink. Does it make a difference ?
lxdoom uses other libraries that are prelinked with
/li
> It shouldn't, since the prelinking failed, but maybe it does. Try
> unprelinking just the lxdoom binary.
It works:
# prelink -u /usr/games/lxdoom
# prelink -u /usr/games/lxdoom-game-server
$ debsums -s lxdoom
[OK]
$ lxdoom
LxDoom v1.4.4 (http://lxdoom.linuxgames.com/)
[...]
So is this a bug
> Output of LD_DEBUG=all lxdoom, please?
Here it is.
--
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/
resu.bz2
Description: application/bzip
On Tue, Mar 09, 2004 at 08:58:29AM -0500, Joe Drew wrote:
> reassign 237033 libc6
> retitle 237033 errno not exported with GLIBC_2.0 version
> thanks
>
> Laurent Bonnaud writes:
> >here is the problem:
> >
> >$ lxdoom
> >lxdoom: relocation error: lxdoom: symbol errno, version GLIBC_2.0 not
> >d
Processing commands for [EMAIL PROTECTED]:
> reassign 237033 libc6
Bug#237033: lxdoom: does not run
Bug reassigned from package `lxdoom' to `libc6'.
> retitle 237033 errno not exported with GLIBC_2.0 version
Bug#237033: lxdoom: does not run
Changed Bug title.
> thanks
Stopping processing here.
reassign 237033 libc6
retitle 237033 errno not exported with GLIBC_2.0 version
thanks
Laurent Bonnaud writes:
here is the problem:
$ lxdoom
lxdoom: relocation error: lxdoom: symbol errno, version GLIBC_2.0 not
defined in file libc.so.6 with link time reference
README.Debian.gz says "The applic
What progress has been made and what still needs to be done?
Apparently current glibc now has the checking code in glibc to prevent it from
being upgraded until *after* the kernel is upgraded (to 2.4.24 or 2.6.0).
However, as Karolina Lindqvist wrote:
> You can't install 2.4.24 on a i386 system,
18 matches
Mail list logo
