Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 9635 - blackdown-jdk -- not showing up with java-config --list-available-vms
Summary: blackdown-jdk -- not showing up with java-config --list-available-vms
Status: RESOLVED DUPLICATE of bug 8755
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Matthew Kennedy (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-25 01:01 UTC by Gentoo Bugs
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 Gentoo Bugs 2002-10-25 01:01:21 UTC
I found this bug (?) while installing openoffice... blackdown-jdk will NOT show
up within my java-config --show-available-vms command... as you can see below...
i shall try with

-----------------------------------------------------------------

1.) emerge openoffice

 * This ebuild has only been tested with the blackdown port of
 * java.  If you use another java implementation, it could fail
 * horribly, so please merge the blackdown-jdk and set it as
 * system VM before proceeding:
 * 
 *  # emerge blackdown-jdk
 *  # java-config --set-system-vm=blackdown-jdk-1.3.1
 *  # env-update
 *  # source /etc/profile
 * 
 * At the time of writing, this was version 1.3.1, so please
 * adjust the version according to the version installed in
 * /opt.
 * 
 * If you however want to test another JDK (not officially supported),
 * you could do the following:
 * 
 *  # export FORCE_JAVA=yes
 * 

!!! ERROR: The ebuild did not complete successfully.
!!! Function pkg_setup, Line 95, Exitcode 0
!!! (no error message)

----------------------------------------------------------------------
2.) emerge blackdown-jdk

<snip>

--- !targe sym /opt/blackdown-jdk-1.3.1/bin/javap
--- !targe sym /opt/blackdown-jdk-1.3.1/bin/javah
--- !targe sym /opt/blackdown-jdk-1.3.1/bin/javadoc
--- !targe sym /opt/blackdown-jdk-1.3.1/bin/javac
--- !targe sym /opt/blackdown-jdk-1.3.1/bin/java
--- !targe sym /opt/blackdown-jdk-1.3.1/bin/jarsigner
--- !targe sym /opt/blackdown-jdk-1.3.1/bin/jar
--- !targe sym /opt/blackdown-jdk-1.3.1/bin/idlj
--- !targe sym /opt/blackdown-jdk-1.3.1/bin/extcheck
--- !targe sym /opt/blackdown-jdk-1.3.1/bin/appletviewer
>>> original instance of package unmerged safely.
>>> Regenerating /etc/ld.so.cache...
>>> dev-java/blackdown-jdk-1.3.1-r7 merged.
>>> Recording dev-java/blackdown-jdk in "world" favorites file...

 * GNU info directory index is up-to-date.

bash-2.05a# 
----------------------------------------------------------------------
3a.) bash-2.05a$ ls /opt/
blackdown-jdk-1.3.1  blackdown-jre-1.3.1
bash-2.05a$ 

3b.) bash-2.05a$ emerge -s blackdown-jdk
Searching...   
[ Results for search key : blackdown-jdk ]
[ Applications found : 1 ]
 
*  dev-java/blackdown-jdk
      Latest version available: 1.3.1-r7
      Latest version installed: 1.3.1-r7
      Homepage: http://www.blackdown.org
      Description: Blackdown Java Development Kit 1.3.1
 
bash-2.05a$ 

3c.) bash-2.05a$ cd /opt/blackdown-jdk-1.3.1/ && ls && pwd
bin  include  include-old  jre	lib  man  share
/opt/blackdown-jdk-1.3.1
bash-2.05a$ 
-------------------------------------------------------------------
4a.) bash-2.05a$ java-config --list-available-vms
[blackdown-jre-1.3.1] Blackdown JRE 1.3.1 (/etc/env.d/java/20blackdown-jre-1.3.1)
bash-2.05a$ 

4b.)bash-2.05a$ emerge -p blackdown-jdk

These are the packages that I would merge, in order.

Calculating dependencies ...done!
[ebuild   R  ] dev-java/blackdown-jdk-1.3.1-r7

bash-2.05a$ 

---------------------------------------------------------------------
Comment 1 Gentoo Bugs 2002-10-25 01:22:24 UTC
err... im sorry i just found a bug report which is the same as this one:

#8755

Sorry Matt will search a little more next time before posting :">
Comment 2 Matthew Kennedy (RETIRED) gentoo-dev 2002-10-25 01:52:42 UTC

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