Bug 139640, Comment #0 - gcc-hardenednopie http://tinyurl.com/qt9h8 - gcc-vanilla (tons of bugs) Huh, not really useful... :( I'd say another eselect-compiler quirk, hard to say since emerge --info does show it (can we have eselect-compiler added to info_pkgs?). Can't reproduce w/ gcc-config-1.3.13-r3.
(In reply to comment #0) > Bug 139640, Comment #0 - gcc-hardenednopie Shows: sys-devel/gcc-config: 1.3.13-r2 so unless the user has done something odd, like installing eselect-compiler but masking gcc-config-2.0.0, then they're not using eselect-compiler. > http://tinyurl.com/qt9h8 - gcc-vanilla (tons of bugs) I couldn't find one here with gcc-config-2, although I didn't check all of them. Bug #68745 shows it on a comment from 2004-10-24, which is long before eselect-compiler existed. Bug #108393 I think is relevant, where emerge's code to retrieve GCC version was reworked (see c#19 et. seq.) Looks to me like this problem has already been fixed in later portage versions. Re-assigning to dev-portage for confirmation.
(In reply to comment #1) > sys-devel/gcc-config: 1.3.13-r2 > so unless the user has done something odd, like installing eselect-compiler but > masking gcc-config-2.0.0, then they're not using eselect-compiler. Nah, eselect-compiler does not depend on gcc-config-2* (which seems to kill wine e.g. - see Bug 138296). Again, I'd really like to see eselect-compiler added to info_pkgs, would make such issues much more clear. > Looks to me like this problem has already been fixed in later portage versions. > Re-assigning to dev-portage for confirmation. Well, it's clearly not the case - see Bug 139640, Comment #0. Has portage-2.1-r1 and it's supposed to be fixed in some of the pre versions (2.1_rc4-r3 according to Bug 108393, Comment #24).
(In reply to comment #2) > Nah, eselect-compiler does not depend on gcc-config-2* (which seems to kill > wine e.g. - see Bug 138296). Again, I'd really like to see eselect-compiler > added to info_pkgs, would make such issues much more clear. I agree. It certainly wouldn't hurt, and anyone with eselect-compiler and gcc-config-1.x installed will see all sorts of strange effects; it'd show that instantly (eselect-compiler users should either have gcc-config-2 or no gcc-config at all). In fact, I've just added it. If it's not appropriate, it can always be removed again. > > Looks to me like this problem has already been fixed in later portage versions. > > Re-assigning to dev-portage for confirmation. > > Well, it's clearly not the case - see Bug 139640, Comment #0. Has > portage-2.1-r1 and it's supposed to be fixed in some of the pre versions > (2.1_rc4-r3 according to Bug 108393, Comment #24). Just had a look at the code in emerge (from 2.1.1_pre2-r2: ---- mystatus, myoutput = commands.getstatusoutput("eselect compiler show") if mystatus == os.EX_OK and len(myoutput.split("/")) == 2: part1, part2 = myoutput.split("/") if part1.startswith(chost + "-"): return myoutput.replace(chost + "-", gcc_ver_prefix, 1) mystatus, myoutput = commands.getstatusoutput("gcc-config -c") if mystatus == os.EX_OK and len(myoutput.split("-")) > 0: return gcc_ver_prefix + myoutput.split("-")[-1] ---- The eselect-compiler part can clearly only report gcc-<version>, unless the config files are seriously fubar. However the gcc-config part would generate 'gcc-vanilla' for the same reason it happened with eselect-compiler on bug #108393, comment #2. If the 'gcc-config -c' output can look like: x86_64-pc-linux-gnu-4.1.1/amd64-vanilla then it'll generate 'gcc-vanilla'. I don't know enough about how that can happen, though; Jeremy referred to multilib profiles for that example, many of the referenced instances don't look like multilib. BTW searching for ", gcc-vanilla" gets rid of all the bugs where people refer to the vanilla compiler as gcc-vanilla :) http://tinyurl.com/lxu33 (13 bugs)
For reference, bug 137786 was similar. I need to know the installed versions of portage, gcc-config, and eselect-compiler. Please also provide the output of `eselect compiler show` and `gcc-config -c`.
(In reply to comment #4) > I need to know the installed versions > of portage, gcc-config, and eselect-compiler. Please also provide the output > of `eselect compiler show` and `gcc-config -c`. Shrug, tough. I requested the info on the 3 bugs that are still open, don't think I would have much luck w/ those that are already fixed. ;)
As requested on bug 135763. [ebuild R ] sys-apps/portage-2.1.1_pre2-r6 [ebuild R ] sys-devel/gcc-config-2.0.0_rc1 [ebuild R ] app-admin/eselect-compiler-2.0.0_rc2-r1 $ gcc-config -c x86_64-pc-linux-gnu-4.1.1/amd64-vanilla $ eselect compiler show x86_64-pc-linux-gnu-4.1.1/amd64-vanilla Worth noting is that portage has been updated since that bug was posted.
(In reply to comment #6) > Worth noting is that portage has been updated since that bug was posted. Could you post also the first line of 'emerge --info' - the one that starts "Portage ..." - thanks.
Portage 2.1.1_pre2-r6 (default-linux/amd64/2006.0, gcc-4.1.1/amd64-vanilla, glibc-2.4.90.20060516-r0, 2.6.17-gentoo x86_64)
as requested on bug 139640 Portage version 2.1-r1 I did not install eselect-compiler gcc-config version 1.3.13-r2 gcc-config -c i686-pc-linux-gnu-3.4.6-hardenednopie
(In reply to comment #9) > gcc-config -c > i686-pc-linux-gnu-3.4.6-hardenednopie The above is the case that base fixed for bug 137786 (fixed in 2.1.1_pre1-r3 and greater, not in 2.1-r1). (In reply to comment #8) > Portage 2.1.1_pre2-r6 (default-linux/amd64/2006.0, gcc-4.1.1/amd64-vanilla, > glibc-2.4.90.20060516-r0, 2.6.17-gentoo x86_64) That seems to be the correct behavior. Please comment if it's not. (In reply to comment #0) > Bug 139640, Comment #0 - gcc-hardenednopie > http://tinyurl.com/qt9h8 - gcc-vanilla (tons of bugs) It seems like this bug is just a duplicate of bug 137786. The problem exists in 2.1-r1 which is the latest stable version, so you can expect to see this in lots of reports. I can release a 2.1-r2 revbump that includes a fix for this and a few other annoying bugs.
(In reply to comment #10) > It seems like this bug is just a duplicate of bug 137786. The problem exists > in 2.1-r1 which is the latest stable version, so you can expect to see this in > lots of reports. I can release a 2.1-r2 revbump that includes a fix for this > and a few other annoying bugs. The bugfix release seems like a good idea (TM), thanks ;)
This is in svn r4056 for 2.1-r2.
This has been released in 2.1-r2.
hi there. It seems the fix is not enough for my box, here is a list of versions of portage that works : 2.1-r2 2.1.1-r1 2.1.2_pre2-r9 All versions above 2.1.2_pre2-r9 caused the bug reported here. # emerge --info Portage 2.1.2_pre2-r9 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.5-r0, 2.6.17-suspend2-r4 i686) ================================================================= System uname: 2.6.17-suspend2-r4 i686 Pentium III (Katmai) Gentoo Base System version 1.12.5 Last Sync: Sun, 29 Oct 2006 02:00:01 +0000 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.4 [disabled] app-admin/eselect-compiler: [Not Present] dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r6 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.60 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.17 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -ftree-vectorize -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/NX/etc /usr/NX/home /usr/lib/X11/xkb /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -ftree-vectorize -pipe -fvisibility-inlines-hidden" DISTDIR="/var/tmp/distfiles" FEATURES="autoconfig distcc distlocks metadata-transfer sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://85.25.128.62 http://ftp.snt.utwente.nl/pub/os/linux/gentoo http://pandemonium.tiscali.de/pub/gentoo/" LANG="fr_FR.UTF-8" LC_ALL="fr_FR.UTF-8" LDFLAGS="-Wl,--as-needed" LINGUAS="en fr ja zh zh_CN" MAKEOPTS="-j6" PKGDIR="/var/tmp/packages" PORTAGE_RSYNC_EXTRA_OPTS="--exclude-from=/etc/portage/rsync-exlude" 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/overlays/portage /usr/portage/local/layman/gentopia /usr/portage/local/layman/liferea_overlay /usr/portage/local/layman/sunrise /usr/portage/local/layman/sunrise /usr/portage/local/layman/wrobel /usr/portage/local/layman/portage-xgl" SYNC="rsync://percolator.esiee.net/gentoo-portage" USE="x86 X a52 aalib acl acpi alsa avahi bash-completion beagle bitmap-fonts bonjour bzip2 cairo canna cdr cjk cli cracklib crypt daap dbus dlloader dri dvd dvdr eds elibc_glibc emboss encode esd evo exif fam fbcon ffmpeg firefox flac freewnn gaim gif glitz glx gnome gnutls gphoto2 gpm gstreamer gtk gtkhtml h264 hal iconv input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdnlog jabber jpeg kernel_linux lcms ldap libg++ libnotify libsexy linguas_en linguas_fr linguas_ja linguas_zh linguas_zh_CN logrotate mad matroska mmx mng mono mp3 mpeg msn musicbrainz ncurses networkmanager nfs nls nptl nptlonly nsplugin ogg opengl pam parse-clocks pcre pdf perl png ppds pppd python quicktime readline reflection samba sasl sdl session silc smp spell spl sqlite sse ssl svg tcpd theora threads tiff truetype truetype-fonts type1-fonts udev unicode usb userland_GNU v4l v4l2 video_cards_r200 video_cards_radeon video_cards_vesa vorbis win32codecs x264 xinerama xml xorg xv xvid zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK
(In reply to comment #14) > All versions above 2.1.2_pre2-r9 caused the bug reported here. > > # emerge --info > Portage 2.1.2_pre2-r9 (default-linux/x86/2006.1/desktop, gcc-4.1.1, Please provide the output of `emerge -V` that demonstrates the symptom of the problem. Also provide the output of `gcc-config -c` and `gcc-config -l`. Note that bug 137786 was recently reopened and fixed in >=portage-2.1.2_pre3-r7.
