Bug 169830 - stabilize sys-apps/busybox-1.4.1-r2 to fix compile issues with current stable
|
Bug#:
169830
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: toolchain@gentoo.org
|
Reported By: chris.bull1@gmail.com
|
|
Component: Core system
|
|
|
URL:
|
|
Summary: stabilize sys-apps/busybox-1.4.1-r2 to fix compile issues with current stable
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-03-07 21:27 0000
|
Hi, I've been upgrading an older gentoo box which I wanted x86stable,
busybox-1.2.2.1 wont compile, my glibc and linux-headers were already updated
to the current stable versions 2.5 & 2.6.17-r2 an unstable version of busybox
(1.4.1-r2)compiles fine.
Reproducible: Always
Steps to Reproduce:
1.emerge busybox
2.
3.
Actual Results:
failed ebuild
Expected Results:
sucessful ebuild
Portage 2.1.2-r9 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.5-r0,
2.6.16-gentoo-r3 i686)
=================================================================
System uname: 2.6.16-gentoo-r3 i686 AMD Athlon(TM) XP 1700+
Gentoo Base System release 1.12.9
Timestamp of tree: Mon, 05 Mar 2007 21:50:01 +0000
dev-lang/python: 2.3.5-r3, 2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
sys-apps/sandbox: 1.2.17
sys-devel/autoconf: 2.13, 2.61
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils: 2.16.1-r3
sys-devel/gcc-config: 1.3.14
sys-devel/libtool: 1.5.22
virtual/os-headers: 2.6.17-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=i686 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.3/env /usr/kde/3.3/share/config
/usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config
/usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/lib/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/splash
/etc/terminfo"
CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distcc distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LANG="en_GB"
LC_ALL="en_GB"
LINGUAS="en_GB"
MAKEOPTS="-j5"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="X alsa apache2 apm berkdb bitmap-fonts cli cracklib crypt cups dri dvb dvd
dvdr dvdread eds emboss encode esd foomaticdb fortran gatos gdbm gif gpm
gstreamer gtk gtk2 iconv imlib immqt isdnlog jpeg kde kdeenablefinal kdexdeltas
libg++ libwww mad midi mikmod motif mp3 mpeg mythtv ncurses nls nptl ogg opengl
oss pam pcre perl png pppd python qt3 qt4 quicktime readline reflection sdl
session spell spl ssl tcpd transcode truetype truetype-fonts type1-fonts v4l
v4l2 vorbis x86 xml xorg xv zlib" ALSA_CARDS="trident" ALSA_PCM_PLUGINS="adpcm
alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa
lfloat linear meter mulaw multi null plug rate route share shm softvol"
ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux"
LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses
text" LINGUAS="en_GB" USERLAND="GNU" VIDEO_CARDS="radeon"
Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS,
PORTAGE_RSYNC_EXTRA_OPTS
Unstable busybox doesn't have this problem. See bug #171695.
Changed Summary to improve searchability.
easier to simply stabilize current unstable
*** Bug 171695 has been marked as a duplicate of this bug. ***
This becomes a problem with SELinux as busybox 1.3* and 1.4* does not compile
with SELinux (bug #160879) so please patch it as the only other options seems
to be adding busybox-1.5.0 with its reworked SELinux-support to the tree and
that is not a good option.
no, that's a dead end development path