From: "Trenton D. Adams" <gentoo-java@adamsbros.org>
To: "Trenton D. Adams" <trent.nospam@telus.net>
Cc: gentoo-java <gentoo-java@lists.gentoo.org>
Subject: Re: [gentoo-java] java-config cannot see JDK
Date: Fri, 18 Aug 2006 14:00:53 -0600 [thread overview]
Message-ID: <44E61C75.7020000@adamsbros.org> (raw)
In-Reply-To: <44E61B65.4040807@telus.net>
Okay, I ended up doing a "equery files" on the java-config packages that
I had installed (v1 and v2). I then ran the check environment thing,
which told me to follow that guide. So, it looks like I do have to.
I'll let you know if it works.
Trenton D. Adams wrote:
> It's been about a month since I updated portage. Does that mean I need
> to follow the upgrade guide?
>
> http://www.gentoo.org/proj/en/java/java-upgrade.xml
>
> Trenton D. Adams wrote:
>> >>> Original instance of package unmerged safely.
>> System Virtual Machine set
>> You may want to update your enviroment by running:
>> "/usr/sbin/env-update && source /etc/profile"
>> >>> Regenerating /etc/ld.so.cache...
>>
>> * After installing blackdown-jdk-1.4.2.03 this
>> * was set as the default JVM to run.
>> * When finished please run the following so your
>> * enviroment gets updated.
>> * /usr/sbin/env-update && source /etc/profile
>> * Or use java-config program to set your preferred VM
>> >>> Regenerating /etc/ld.so.cache...
>> >>> dev-java/blackdown-jdk-1.4.2.03 merged.
>> >>> Recording dev-java/blackdown-jdk in "world" favorites file...
>>
>>
>> abda vhosts.d # java-config -L
>>
>> The above results in no output.
>>
>> Any ideas?
--
gentoo-java@gentoo.org mailing list
prev parent reply other threads:[~2006-08-18 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 19:29 [gentoo-java] java-config cannot see JDK Trenton D. Adams
2006-08-18 19:45 ` Greg Tassone
[not found] ` <44E61B65.4040807@telus.net>
2006-08-18 20:00 ` Trenton D. Adams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44E61C75.7020000@adamsbros.org \
--to=gentoo-java@adamsbros.org \
--cc=gentoo-java@lists.gentoo.org \
--cc=trent.nospam@telus.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox