Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 38776 - Blackdown-jdk-1.4.1 ebuild misidentifies gcc version
Summary: Blackdown-jdk-1.4.1 ebuild misidentifies gcc version
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Java team
URL: http://forums.gentoo.org/viewtopic.ph...
Whiteboard:
Keywords:
: 38821 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-01-19 21:30 UTC by Jason Warner
Modified: 2004-06-06 19:46 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Warner 2004-01-19 21:30:38 UTC
The blackdown-jdk-1.4.1 ebuild fails to properly identify the correct gcc version and defaults to gcc-3.2.bin.  My system does not have 3.2.

gentoo jwarner # gcc-config -c
i686-pc-linux-gnu-2.95.3
gentoo jwarner # gcc -dumpversion
2.95.3

It looks like bug 21626 was submitted for this same problem though I don't understand why the resolution is resolved and the status is won't fix.  I would think there are plenty of systems still running gcc-2.95.  There are some postings in the forums about this bug causing problems for gettext among other packages.

This issue was causing problems for the getttext ebuild and would give me an error like /usr/opt/blackdown-jdk-1.4.1/jre/lib/i386/client/libjvm.so, because libstdc++.so.5: cannot open shared object file: No such file or directory when I tried to do a java -version command.  To resolve I edited the blackdown-jdk-1.4.1 ebuild like so:

#if [ "`gcc -dumpversion | cut -f1 -d.`" -eq "3" -a "`gcc -dumpversion | cut -f2 -d.`" -ge "2" ] ; then
#   SRC_URI="x86? ( ${J_URI}/i386/${JREV}/j2sdk-${PV}-${JREV}-linux-i586-gcc3.2.bin )
#       amd64? ( ${J_URI}/i386/${JREV}/j2sdk-${PV}-${JREV}-linux-i586-gcc3.2.bin )"
#else
SRC_URI="x86? ( ${J_URI}/i386/${JREV}/j2sdk-${PV}-${JREV}-linux-i586-gcc2.95.bin )"
#fi
#SRC_URI="${SRC_URI} sparc? ( ${J_URI}/sparc/${JREV}/j2sdk-${PV}-${JREV}-linux-sparc-gcc3.2.bin )"

This forced the blackdown-jdk-1.4.1 ebuild to use the proper file (gcc-2.95).  This also enable me to successfully compile gettext.

Reproducible: Always
Steps to Reproduce:
1.  Start with Gentoo system with gcc version 2.95
2.  Emerge blackdown-jdk-1.4.1
3.  Do a java -version or try and compile gettext and you will see something to the effect of:  /usr/opt/blackdown-jdk-1.4.1/jre/lib/i386/client/libjvm.so, because libstdc++.so.5: cannot open shared object file: No such file or directory.
Actual Results:  
/usr/opt/blackdown-jdk-1.4.1/jre/lib/i386/client/libjvm.so, because 
libstdc++.so.5: cannot open shared object file: No such file or directory

Expected Results:  
gentoo jwarner # java -
version                                                        
java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.1-01)
Java HotSpot(TM) Client VM (build Blackdown-1.4.1-01, mixed mode)

or

>>> Regenerating /etc/ld.so.cache...
 * Caching service 
dependencies...                                                                 
                     [ ok ]
>>> sys-devel/gettext-0.12.1 merged.
>>> Recording sys-devel/gettext in "world" favorites file...

http://forums.gentoo.org/viewtopic.php?p=792394#792394
Comment 1 Adrian Almenar 2004-01-20 03:57:50 UTC
Ok, ill try to check this.

Can you post the output of "emerge info", please ?
Comment 2 Jason Warner 2004-01-20 07:33:55 UTC
root@gentoo jwarner # emerge info
Portage 2.0.49-r20 (default-1.0, gcc-2.95.3, glibc-2.2.5-r9, 2.4.22-gentoo-r5)
=================================================================
System uname: 2.4.22-gentoo-r5 i686 AMD Athlon(tm) Processor
Gentoo Base System version 1.4.3.10p1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=i686 -O2 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /opt/glftpd/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/bind /var/qmail/alias /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=i686 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnow apache2 berkdb cdr crypt cups encode gdbm gif gpm imap imlib innodb jpeg lcms libg++ libwww matrox mmx motif mysql ncurses nls oss pam perl png python readline samba scanner sdl slang snmp spell ssl svga tcltk tcpd truetype vhost x86 xml xml2"
Comment 3 Adrian Almenar 2004-01-20 16:04:05 UTC
*** Bug 38821 has been marked as a duplicate of this bug. ***
Comment 4 Alexander Gabert (RETIRED) gentoo-dev 2004-03-03 05:16:10 UTC
did this change make it into the blackdown ebuild as it was expected by the user?
Comment 5 Aron Griffis (RETIRED) gentoo-dev 2004-06-06 19:46:02 UTC
Ok, I think I fixed this.  Please re-open if it still doesn't work for you.