126559 – prod busybox incompatible with glibc2.4 - need update from ~x86

Bug 126559 - prod busybox incompatible with glibc2.4 - need update from ~x86

Summary: prod busybox incompatible with glibc2.4 - need update from ~x86

Status:	RESOLVED DUPLICATE of bug 126029

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	x86 Linux

Importance:	High minor (vote)
Assignee:	Embedded Gentoo Team

URL:	http://forums.gentoo.org/viewtopic.ph...
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-03-17 10:12 UTC by Trevor Bowen
Modified:	2006-03-17 11:38 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Trevor Bowen 2006-03-17 10:12:10 UTC

Please see above URL for more info...

Basic problem is that prod version of busybox cannot be compiled with new glibc2.4.  I was forced to emerge the ~x86 version of busybox, just to rebuild my system with "emerge -e system".

Here's emerge info...

Portage 2.0.54 (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.4-r0, 2.6.15-gentoo-r1 i686)
=================================================================
System uname: 2.6.15-gentoo-r1 i686 Pentium II (Deschutes)
Gentoo Base System version 1.6.14
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=pentium2 -O3 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/alias /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium2 -O3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa apache2 audiofile bash-completion berkdb bitmap-fonts bzip2 cli crypt ctype dba dri eds emacs emboss esd expat fam fastbuild force-cgi-redirect fortran ftp gd gif gpm gstreamer imlib ipv6 jpeg lcms libg++ libwww memlimit mhash mng motif mp3 mpeg mysql ncurses nls nptl nptlonly ogg opengl pam pcre pdflib perl php png posix python readline sdl session simplexml slang snmp soap sockets spell spl ssl svga tcltk tcpd tiff tokenizer truetype truetype-fonts type1-fonts udev usb vhosts vorbis x86 xml xml2 xsl xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY

Comment 1 solar (RETIRED) gentoo-dev

2006-03-17 10:22:36 UTC

1) do not paste links to forums. That really makes most devs angry.
2) This is a dupe of another bug
3) This is fixed in ~arch. Use that. We are not fixing packages in stable for ~arch glibc

Comment 2 SpanKY gentoo-dev

2006-03-17 10:32:15 UTC


*** This bug has been marked as a duplicate of 126029 ***

Comment 3 Trevor Bowen 2006-03-17 11:38:03 UTC

Thanks for the tips on bugzilla ettiquete... :-)

I did not realize that glibc2.4 was part of ~arch.  I thought it was stable.  My bad.