Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 38821 - Blackdown-jdk-1.4.1 ebuild misidentifies gcc version
Summary: Blackdown-jdk-1.4.1 ebuild misidentifies gcc version
Status: RESOLVED DUPLICATE of bug 38776
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:
Depends on:
Blocks:
 
Reported: 2004-01-20 07:31 UTC by Jason Warner
Modified: 2005-07-17 13:06 UTC (History)
0 users

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-20 07:31:21 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 16:04:04 UTC

*** This bug has been marked as a duplicate of 38776 ***