Bug#453340: mldonkey-server: Mldonkey-server compiled with glibc6 and now SID use glibc2.7

2007-12-13 Thread spiral voice

Hi,

you can ignore this warning message.

It was created because users used a glibc-2.3 linked version on
a glibc-2.2 system which core dumps in iconv functions when
a GUI connects to the core.

glibc 2.3 is not to problematic in this regard.

Greetings, spiralvoice

_
Windows Live Fotogalerie: So einfach organisieren Sie Ihre Fotos!
http://get.live.com/photogallery/overview 



Bug#453340: mldonkey-server: Mldonkey-server compiled with glibc6 and now SID use glibc2.7

2007-12-13 Thread Samuel Mimram

Hi,

Sergi Barroso wrote:

Yes, it's so simple, if you run current mldonkey server on Debian with
libc 2.7 it doesn't run. After I compiled debian source package it works
correctly.


Could you be more precise please? What happens exactly if you run the 
mldonkey command? Could you paste the output?


Upstream confirmed that the warning message could be ignored so your 
problem might be unrelated to this... I can run mldonkey without any 
problem here even though I see the warning message.


Cheers,

Samuel.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#453340: mldonkey-server: Mldonkey-server compiled with glibc6 and now SID use glibc2.7

2007-12-13 Thread Sergi Barroso

# Hi,
#
# Sergi Barroso Terradas wrote:
# This core is running with glibc 2.7 but it was compiled with glibc
# 2.6.1.
# This can lead to unexpected behaviour. Consider compiling the core
# yourself
# or getting a binary compiled with glibc 2.6.1.
#
# Actually version of glibc for Debian SID is 2.7, mldonkey new to be
# recompiled for SID version.
#
# I don't really understand how this could lead to problems: either the
# libc 2.6.1 and 2.7 are ABI-incompatible (and in this case the later
# should have a different SONAME) or they are ABI-compatible, which I
# believe is the case, and we should be able to use a binary compiled with
# the 2.6.1 version with the 2.7 version without any problem.
#
# Do you have a precise example of problems this could cause?
#
# Cheers,
#
# Samuel.
#

Yes, it's so simple, if you run current mldonkey server on Debian with
libc 2.7 it doesn't run. After I compiled debian source package it works
correctly.

-- 
  Sergi Barroso
  Linux user #313577
  PGPID: 287913B4
  http://www.lionclan.org




Bug#453340: mldonkey-server: Mldonkey-server compiled with glibc6 and now SID use glibc2.7

2007-12-13 Thread Sergi Barroso
El Jueves, 13 de Diciembre de 2007, escribió:
 Hi,

 Sergi Barroso wrote:
  Yes, it's so simple, if you run current mldonkey server on Debian with
  libc 2.7 it doesn't run. After I compiled debian source package it works
  correctly.

 Could you be more precise please? What happens exactly if you run the
 mldonkey command? Could you paste the output?

The output from command line is:

This can lead to unexpected behaviour. Consider compiling the core yourself 
or getting a binary compiled with glibc 2.6.1.


 Upstream confirmed that the warning message could be ignored so your
 problem might be unrelated to this... I can run mldonkey without any
 problem here even though I see the warning message.

 Cheers,

 Samuel.



-- 

 Sergi Barroso
 Linux user #313577
 PGPID: 287913B4
 http://www.lionclan.org



signature.asc
Description: This is a digitally signed message part.


Bug#453340: mldonkey-server: Mldonkey-server compiled with glibc6 and now SID use glibc2.7

2007-12-12 Thread Samuel Mimram

Hi,

Sergi Barroso Terradas wrote:

This core is running with glibc 2.7 but it was compiled with glibc
2.6.1.
This can lead to unexpected behaviour. Consider compiling the core
yourself
or getting a binary compiled with glibc 2.6.1.

Actually version of glibc for Debian SID is 2.7, mldonkey new to be
recompiled for SID version.


I don't really understand how this could lead to problems: either the 
libc 2.6.1 and 2.7 are ABI-incompatible (and in this case the later 
should have a different SONAME) or they are ABI-compatible, which I 
believe is the case, and we should be able to use a binary compiled with 
the 2.6.1 version with the 2.7 version without any problem.


Do you have a precise example of problems this could cause?

Cheers,

Samuel.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#453340: mldonkey-server: Mldonkey-server compiled with glibc6 and now SID use glibc2.7

2007-11-28 Thread Sergi Barroso Terradas
Package: mldonkey-server
Version: 2.9.2-2
Severity: important

Mlnet shows:

This core is running with glibc 2.7 but it was compiled with glibc
2.6.1.
This can lead to unexpected behaviour. Consider compiling the core
yourself
or getting a binary compiled with glibc 2.6.1.

Actually version of glibc for Debian SID is 2.7, mldonkey new to be
recompiled for SID version.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.23-kamikaze4 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]