While I must admit that I don't understand a lot of what you're
telling me (and that's my fault - not yours), I did take a look at the
symlink I created in /etc/alternatives for javac...
... what do you know - in the file manager it said that the file I
linked to didn't exist - I noticed that the path was wrong. I deleted
it, ran the command to create the symlink again (this time with the
right path), and now it works.
Thanks a _ton_ for being so patient.
Now all I have to do is get Ruby up and working, then sit on it for a
while, to be convinced that Debian is my platform of choice.
-Rich
P.s. - I have another admission - I still don't get what step 7 in
your walkthrough does...
On Wed, 03 Nov 2004 14:46:00 -0700, Von Fugal <[EMAIL PROTECTED]> wrote:
> * me lyman [Wed, 3 Nov 2004 at 14:26 -0700]
> > When I go through all of the steps, it ends up giving me the right
> > information for java -version (1.5.0), but when I ask for javac
> > -version it says:
> >
> > debwin:~# bash: javac: command not found
> Setup a link to point to the alternatives file, or just skip that and
> link directly to the executable, see below...
>
> > Also - when I ran the update-alternatives commands ( --config java and
> > --config javac ) it said:
> >
> > There is only 1 program which provides java
> > (/usr/bin/java-vm). Nothing to configure.
> >
> > ... and...
> >
> > There is only 1 program which provides javac
> > (/usr/local/lib/jdk/bin/javac). Nothing to configure.
>
> You're almost there. This alternatives configuration means that there is
> a link named javac (/etc/alternatives/javac) which now points to
> /usr/local/lib/jdk/bin/javac. Now you can link /usr[/local]/bin/javac to
> /etc/alternatives/javac ('cd /usr/bin/; ln -s /etc/alternatives/javac').
> This is usefull if later on you install some other java compiler like
> kaffe or whatever, then all you have to do is run update-alternatives to
> use whichever one you feel like. You could, of course, also just link
> /usr/bin/javac directly to /usr/local/lib/jdk/bin/javac, if you don't
> feel like messing with the alternatives approach.
>
> The java interpreter should be good to go already. If not, then you just
> need to edit /etc/java-vm . First line is the path to the 'java'
> program, the second line is your classpath configuration. (list of colon
> seperated paths)
>
> Hope that helps.
>
> Von Fugal
>
>
> ____________________
> BYU Unix Users Group
> http://uug.byu.edu/
> ___________________________________________________________________
> List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
>
>
>
____________________
BYU Unix Users Group
http://uug.byu.edu/
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
