# emerge --info !!! Relying on the shell to locate gcc, this may break !!! DISTCC, installing gcc-config and setting your current gcc !!! profile will fix this Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r1, 2.6.12-gentoo-r6 i686) ================================================================= deena / # gcc-config -l env: envvar: No such file or directory * /usr/bin/gcc-config: Could not get portage CHOST! * /usr/bin/gcc-config: No gcc profile is active; please select one! [1] i686-pc-linux-gnu-3.4.4 [2] i686-pc-linux-gnu-3.4.4-hardened [3] i686-pc-linux-gnu-3.4.4-hardenednopie [4] i686-pc-linux-gnu-3.4.4-hardenednopiessp [5] i686-pc-linux-gnu-3.4.4-hardenednossp deena / # gcc-config 1 * Switching to i686-pc-linux-gnu-3.4.4 compiler ... [ ok ] deena / # gcc-config -l env: envvar: No such file or directory * /usr/bin/gcc-config: Could not get portage CHOST! * /usr/bin/gcc-config: No gcc profile is active; please select one! [1] i686-pc-linux-gnu-3.4.4 [2] i686-pc-linux-gnu-3.4.4-hardened [3] i686-pc-linux-gnu-3.4.4-hardenednopie [4] i686-pc-linux-gnu-3.4.4-hardenednopiessp [5] i686-pc-linux-gnu-3.4.4-hardenednossp Reproducible: Always Steps to Reproduce: 1. emerge gcc-config-1.4.0 2. b0rk your system 3. Actual Results: gcc-config does not work. portage cannot find gcc. Expected Results: functional toolkit. # emerge --info !!! Relying on the shell to locate gcc, this may break !!! DISTCC, installing gcc-config and setting your current gcc !!! profile will fix this Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r1, 2.6.12-gentoo-r6 i686) ================================================================= System uname: 2.6.12-gentoo-r6 i686 AMD Athlon(tm) XP 2000+ Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -mtune=athlon-xp -pipe -O3 -fweb -frename-registers -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium3 -mtune=pentium3 -pipe -O3 -fweb -frename-registers -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apm arts avi berkdb bitmap-fonts crypt cups eds emboss encode foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imlib ipv6 jpeg kde libg++ libwww mad mikmod motif mp3 mpeg ncurses nls nptl ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl spell ssl tcpd truetype truetype-fonts type1-fonts vorbis xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS # emerge gcc-config Calculating dependencies ...done! >>> emerge (1 of 1) sys-devel/gcc-config-1.4.0 to / >>> Unpacking source... >>> Source unpacked. >>> Test phase [not enabled]: sys-devel/gcc-config-1.4.0 >>> Install gcc-config-1.4.0 into /var/tmp/portage/gcc-config-1.4.0/image/ category sys-devel man: prepallstrip: strip: i686-pc-linux-gnu-strip --strip-unneeded strip: i686-pc-linux-gnu-strip --strip-unneeded usr/lib/misc/gcc-config-wrapper >>> Completed installing gcc-config-1.4.0 into /var/tmp/portage/gcc-config-1.4.0/image/ >>> Merging sys-devel/gcc-config-1.4.0 to / --- /usr/ --- /usr/bin/ >>> /usr/bin/gcc-config --- /usr/lib/ --- /usr/lib/misc/ >>> /usr/lib/misc/gcc-config-wrapper >>> Safely unmerging already-installed instance... --- !mtime obj /usr/lib/misc/gcc-config-wrapper --- !mtime obj /usr/bin/gcc-config --- !empty dir /usr/lib/misc --- !empty dir /usr/lib --- !empty dir /usr/bin --- !empty dir /usr >>> original instance of package unmerged safely. >>> Regenerating /etc/ld.so.cache... >>> sys-devel/gcc-config-1.4.0 merged. >>> clean: No packages selected for removal. >>> Auto-cleaning packages ... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. # gcc-config -l env: envvar: No such file or directory * /usr/bin/gcc-config: Could not get portage CHOST! * /usr/bin/gcc-config: No gcc profile is active; please select one! [1] i686-pc-linux-gnu-3.4.4 [2] i686-pc-linux-gnu-3.4.4-hardened [3] i686-pc-linux-gnu-3.4.4-hardenednopie [4] i686-pc-linux-gnu-3.4.4-hardenednopiessp [5] i686-pc-linux-gnu-3.4.4-hardenednossp # gcc-config 1 * Switching to i686-pc-linux-gnu-3.4.4 compiler ... [ ok ] # gcc-config -l env: envvar: No such file or directory * /usr/bin/gcc-config: Could not get portage CHOST! * /usr/bin/gcc-config: No gcc profile is active; please select one! [1] i686-pc-linux-gnu-3.4.4 [2] i686-pc-linux-gnu-3.4.4-hardened [3] i686-pc-linux-gnu-3.4.4-hardenednopie [4] i686-pc-linux-gnu-3.4.4-hardenednopiessp [5] i686-pc-linux-gnu-3.4.4-hardenednossp # portageq envvar CHOST i686-pc-linux-gnu and finally, the solution to the problem: # cat /etc/portage/package.mask #sys-kernel/gentoo-dev-sources-2.6.11-r4 it looks like the latest addition to the portage tree is b0rken.
there is no gcc-config-1.4.0
there is no gcc-config-1.4.0? what a joke. there's no need to lie about the situation. the file mistakenly found its way into the snapshot portage-20050827.tar.bz2, and you fixed the problem by removing the ebuild from portage. i don't have any problems with developers admitting that mistakes have been made and promptly fixing the problem. i do take issue with the way that you quietly made the problem go away and then called me a liar. anyone who looks at the file portage-20050827.tar.bz2 will find that i'm telling the truth. fixing the bug by erasing the file does not constitute an INVALID resolution. it is a VERIFIED bug that you've fixed. but sweeping the bug under the carpet does make your statistics look better, doesn't it?
i dont know wtf your problem is but you need to chill out at no time was gcc-config-1.4.0 ever available in the stable or unstable trees ... it was package.masked the entire time it was in portage it has since been removed this bug is INVALID because the only way for you to get gcc-config 1.4.0 onto your system was to change maskings that we had in place
ok, i have chilled. i think that you need to take a close look at the portage snapshot for the 27th and you'll find that your assertions are mistaken. you might also want to read the referenced thread above, as it clearly shows that the offensive ebuild was in the portage tree in an unmasked state as of the snapshot on the 27th and when i emerged it onto three systems 24 hours ago. this isn't a case where i have unmasked the ebuild. this is a case where there was a legitimate mistake in the portage tree. i find it very difficult to understand why you cannot admit that there was an error in the portage tree, or why you insist on attempting to shift blame to the user who reports the error. that is just wrong.
if you read the log files from cvs, gcc-config-1.4.0 was deleted Aug 9th while the package.mask entry was not removed until Aug 20th i'm not responsible in anyway for snapshots so i cannot vouch that they are not broken
i am at a loss to explain why the bug occurred or how it was fixed, but even so i am glad that the situation has been resolved. thank you for your time.
