Debian Bug report logs - #193310
libc6: gconv breaks for statically-compiled binaries

version graph

Package: libc6; Maintainer for libc6 is GNU Libc Maintainers <debian-glibc@lists.debian.org>; Source for libc6 is src:eglibc.

Reported by: Joe Drew <drew@debian.org>

Date: Wed, 14 May 2003 15:33:02 UTC

Severity: normal

Found in version 2.3.1-17

Done: GOTO Masanori <gotom@debian.or.jp>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, GNU Libc Maintainers <debian-glibc@lists.debian.org>, glibc@packages.qa.debian.org:
Bug#193310; Package libc6. Full text and rfc822 format available.

Acknowledgement sent to Joe Drew <drew@debian.org>:
New Bug report received and forwarded. Copy sent to GNU Libc Maintainers <debian-glibc@lists.debian.org>, glibc@packages.qa.debian.org. Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Joe Drew <drew@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: libc6: gconv breaks for statically-compiled binaries
Date: Wed, 14 May 2003 11:19:53 -0400
Package: libc6
Version: 2.3.1-17
Severity: normal

When I compile a binary statically which uses iconv(), and then deploy
that binary on a glibc 2.2.5 machine, it fails:

albatross:/# /usr/local/bin/msgfmt -o de.gmo de.po
/usr/local/bin/msgfmt: iconv failure: Argument list too long

This, I believe, is because of some incompatible change in gconv. While
the statically-compiled binary includes gconv() from glibc 2.3.1, the
/usr/lib/gconv .so files are compiled against glibc 2.2.5.

This indicates to me that some backwards-incompatible change has
happened. This may or may not be desired behaviour; feel free to close
this bug if this operation is intentionally unsupported.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux albatross 2.4.20 #3 Wed May 7 12:12:41 EDT 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages libc6 depends on:
ii  libdb1-compat                 2.1.3-7    The Berkeley database routines [gl

-- no debconf information




Information forwarded to debian-bugs-dist@lists.debian.org, GNU Libc Maintainers <debian-glibc@lists.debian.org>, glibc@packages.qa.debian.org:
Bug#193310; Package libc6. Full text and rfc822 format available.

Acknowledgement sent to Daniel Jacobowitz <dan@debian.org>:
Extra info received and forwarded to list. Copy sent to GNU Libc Maintainers <debian-glibc@lists.debian.org>, glibc@packages.qa.debian.org. Full text and rfc822 format available.

Message #10 received at 193310@bugs.debian.org (full text, mbox):

From: Daniel Jacobowitz <dan@debian.org>
To: Joe Drew <drew@debian.org>, 193310@bugs.debian.org
Subject: Re: Bug#193310: libc6: gconv breaks for statically-compiled binaries
Date: Wed, 14 May 2003 20:06:48 -0400
On Wed, May 14, 2003 at 11:19:53AM -0400, Joe Drew wrote:
> Package: libc6
> Version: 2.3.1-17
> Severity: normal
> 
> When I compile a binary statically which uses iconv(), and then deploy
> that binary on a glibc 2.2.5 machine, it fails:
> 
> albatross:/# /usr/local/bin/msgfmt -o de.gmo de.po
> /usr/local/bin/msgfmt: iconv failure: Argument list too long
> 
> This, I believe, is because of some incompatible change in gconv. While
> the statically-compiled binary includes gconv() from glibc 2.3.1, the
> /usr/lib/gconv .so files are compiled against glibc 2.2.5.
> 
> This indicates to me that some backwards-incompatible change has
> happened. This may or may not be desired behaviour; feel free to close
> this bug if this operation is intentionally unsupported.

I'll leave the bug in case anyone else has comments, but this is a
known issue - static binaries really just aren't portable between glibc
2.2 and 2.3, for both this and NSS reasons.  Sucks.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer



Information forwarded to debian-bugs-dist@lists.debian.org, GNU Libc Maintainers <debian-glibc@lists.debian.org>, glibc@packages.qa.debian.org:
Bug#193310; Package libc6. Full text and rfc822 format available.

Acknowledgement sent to GOTO Masanori <gotom@debian.or.jp>:
Extra info received and forwarded to list. Copy sent to GNU Libc Maintainers <debian-glibc@lists.debian.org>, glibc@packages.qa.debian.org. Full text and rfc822 format available.

Message #15 received at 193310@bugs.debian.org (full text, mbox):

From: GOTO Masanori <gotom@debian.or.jp>
To: Daniel Jacobowitz <dan@debian.org>, 193310@bugs.debian.org
Cc: Joe Drew <drew@debian.org>
Subject: Re: Bug#193310: libc6: gconv breaks for statically-compiled binaries
Date: Sat, 17 May 2003 02:32:13 +0900
At Wed, 14 May 2003 20:06:48 -0400,
Daniel Jacobowitz wrote:
> 
> On Wed, May 14, 2003 at 11:19:53AM -0400, Joe Drew wrote:
> > Package: libc6
> > Version: 2.3.1-17
> > Severity: normal
> > 
> > When I compile a binary statically which uses iconv(), and then deploy
> > that binary on a glibc 2.2.5 machine, it fails:
> > 
> > albatross:/# /usr/local/bin/msgfmt -o de.gmo de.po
> > /usr/local/bin/msgfmt: iconv failure: Argument list too long
> > 
> > This, I believe, is because of some incompatible change in gconv. While
> > the statically-compiled binary includes gconv() from glibc 2.3.1, the
> > /usr/lib/gconv .so files are compiled against glibc 2.2.5.
> > 
> > This indicates to me that some backwards-incompatible change has
> > happened. This may or may not be desired behaviour; feel free to close
> > this bug if this operation is intentionally unsupported.
> 
> I'll leave the bug in case anyone else has comments, but this is a
> known issue - static binaries really just aren't portable between glibc
> 2.2 and 2.3, for both this and NSS reasons.  Sucks.

Yup.  It's currently "intentionally unsupported."  I think it's ok to
close it.

Regards,
-- gotom




Reply sent to GOTO Masanori <gotom@debian.or.jp>:
You have taken responsibility. Full text and rfc822 format available.

Notification sent to Joe Drew <drew@debian.org>:
Bug acknowledged by developer. Full text and rfc822 format available.

Message #20 received at 193310-done@bugs.debian.org (full text, mbox):

From: GOTO Masanori <gotom@debian.or.jp>
To: Joe Drew <drew@debian.org>, 193310-done@bugs.debian.org
Subject: Re: Bug#193310: libc6: gconv breaks for statically-compiled binaries
Date: Thu, 22 May 2003 12:59:34 +0900
At Sat, 17 May 2003 02:32:13 +0900,
GOTO Masanori wrote:
> 
> At Wed, 14 May 2003 20:06:48 -0400,
> Daniel Jacobowitz wrote:
> > 
> > On Wed, May 14, 2003 at 11:19:53AM -0400, Joe Drew wrote:
> > > Package: libc6
> > > Version: 2.3.1-17
> > > Severity: normal
> > > 
> > > When I compile a binary statically which uses iconv(), and then deploy
> > > that binary on a glibc 2.2.5 machine, it fails:
> > > 
> > > albatross:/# /usr/local/bin/msgfmt -o de.gmo de.po
> > > /usr/local/bin/msgfmt: iconv failure: Argument list too long
> > > 
> > > This, I believe, is because of some incompatible change in gconv. While
> > > the statically-compiled binary includes gconv() from glibc 2.3.1, the
> > > /usr/lib/gconv .so files are compiled against glibc 2.2.5.
> > > 
> > > This indicates to me that some backwards-incompatible change has
> > > happened. This may or may not be desired behaviour; feel free to close
> > > this bug if this operation is intentionally unsupported.
> > 
> > I'll leave the bug in case anyone else has comments, but this is a
> > known issue - static binaries really just aren't portable between glibc
> > 2.2 and 2.3, for both this and NSS reasons.  Sucks.
> 
> Yup.  It's currently "intentionally unsupported."  I think it's ok to
> close it.             ^unfortunately unwillingly intentionally unsupported

And I close it.

Regards,
-- gotom



Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sat Apr 19 07:45:44 2014; Machine Name: beach.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.