Quote:
Originally posted by Unregistered
perl-Msgcat-1.03-7mdk
libsigc++1.0-1.0.3-2mdk
gcc-cpp-2.96-0.62mdk
gcc-2.96-0.62mdk
gcc3.0-cpp-3.0.1-1mdk
gcc-c++-2.96-0.62mdk
gcombust-0.1.46-1mdk
Nope, no gccjava. Anyway, when you said to add JAVA_HOME to my path, I did add it to the beginning, not the end, and it still didn't work. <sigh>
If my perfectly normal out-of-the-box Mandrake installation (plus the Sun JRE) worked fine with LimeWire 2.3 and not LimeWire 2.4, then I think there is a bug in LimeWire 2.4. 
Maybe I'll try the installer version... The only reason I didn't use it to begin with was spyware fears... |
we can simply put /usr/java/j2re1.4.0/bin at the beginning. It really needs the path pointing to the bin of the java installation. Creating JAVA_HOME is created only to make it easier to change java versions on the fly at the commandline for purposes such as mine. You can simply set that into your path stateeent pointing to the "bin" and then log out and then back in. That is the best sure fire way to activate and use the changes as they are not always going to be used by simply opening up a new terminal or different terminal window when you are in a window manager. As it may not take effect simply because you may have already used an instance of that window prior to the changes. I had similiar effects until I did that. It is guaranteed to work.
altoine