Portage apparently downloads the wrong Blackdown 1.4.1 binaries on old Gentoo systems (i.e not 1.4 systems!) Reproducible: Always Steps to Reproduce: 1.emerge blackdown-1.4.1.ebuild on a non-1.4 gentoo system Actual Results: It tries to emerge the wrong blackdown binaries! Expected Results: It should have emerged 2.95.3 blackdown binaries Portage 2.0.48 (default-1.0, gcc-2.95.3, glibc-2.2.5-r8) ================================================================= System uname: 2.4.20 i686 AMD Athlon(tm) XP 1800+ GENTOO_MIRRORS="ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ rsync://ftp.belnet.be/gentoo/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb:/usr/kde/3.1/share/config:/usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm arts avi crypt cups encode jpeg kde libg++ mikmod mmx mpeg ncurses pdflib quicktime spell truetype xml2 xmms xv berkdb cdr esd gdbm gif gnome-libs gpm gtk imlib java libwww motif mozilla mysql nls oggvorbis opengl pam perl png python qt readline scanner sdl slang ssl svga tcltk tcpd tetex tiff X" COMPILER="" CHOST="i686-pc-linux-gnu" CFLAGS="-march=i686 -O3 -pipe" CXXFLAGS="-march=i686 -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.local.munted.org.uk/gentoo-portage" FEATURES="sandbox ccache fixpackages"
The ebuild for blackdown jdk 1.4.1 examines gcc-major-version and gcc-minor-version to download the correct binaries. Where does these comes from? I think this is why emerge fails.
gcc-config prints your gcc installed versions on 1.4 GCC="3" is set works here fine on 3 of my systems (old and new ones) watch out /etc/env.d/05gcc
Here's /etc/env.d/05gcc PATH="/usr/i686-pc-linux-gnu/gcc-bin/2.95" ROOTPATH="/usr/i686-pc-linux-gnu/gcc-bin/2.95" MANPATH="/usr/share/gcc-data/i686-pc-linux-gnu/2.95/man" INFOPATH="/usr/share/gcc-data/i686-pc-linux-gnu/2.95/info" CC="gcc" CXX="g++" LDPATH="/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.3:/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2"
Change a line in /usr/portage/dev-java/blackdown-jdk/blackdown-jdk-1.4.1.ebuild from: if [ "`gcc-major-version`" -eq "3" -a "`gcc-minor-version`" -ge "2" ] ; then to this: if [ `gcc-major-version` -eq 3 -a `gcc-minor-version` -ge 2 ] ; then fixes the problem for me. Can the ebuild be changed, please?
please provide #gcc-config -l
[alex@slut]/home/alex > gcc-config -l [1] i686-pc-linux-gnu-2.95.3 [2] i686-pc-linux-gnu-3.2.2
wontfix and invalid if [ `gcc-major-version` -eq 3 -a `gcc-minor-version` -ge 2 ] ; then isn't working, so it's installing the old version cause you have both gcc versions installed (automatic getting higher version) 3.2 binary would be installed, even if you wan't 2.95
Well, that's wrong - it ought to be using the current gcc profile. How do I reopen this bug report?
so what do you really want ? 1.2 with glibc 2.2 and gcc 2.95 or 1.4 with glibc 2.3 and gcc 3.x
If by 1.2 and 1.4 you mean gentoo releases, then yes I would like to be able to us e blackdown JDK 1.4.1 (2.95) with 1.2, and blackdown JDK 1.4.1 (3.2) with 1.4.
you can have only one gentoo release at a time 1.2 OR 1.4
Forgive me, I think I've got my wires crossed somewhere. I have two boxes, one is Gentoo 1.4, has gcc 3.2.2 as default, it correctly installs blackdown jdk 1.4.1 3.2 binaries, on the other box, it is Gentoo 1.2, has gcc 2.95.3 as default (but also has gcc 3.2.2 - I only switch to it to build OpenOffce), it incorrectly installs blackdown jdk 1.4.1 3.2 binaries. Am I missing something here? My apologies if I am.
marking this as wontfix this is really not a typical configuration.
