Gnutella Forums

Gnutella Forums (https://www.gnutellaforums.com/)
-   General Linux Support (https://www.gnutellaforums.com/general-linux-support/)
-   -   The Solution To All Install Problems (https://www.gnutellaforums.com/general-linux-support/11187-solution-all-install-problems.html)

nDiScReEt May 9th, 2002 01:47 AM

The Solution To All Install Problems
 
<center>
<blockquote>
ooooooooooooooooooooooooooooooooooooo
0 NOTE 0
ooooooooooooooooooooooooooooooooooooo
This is 100% guaranteed to work in a Bourne Again shell environment (bash or sh). Especially, if it is followed to the letter. Never Install LimeWire as ROOT!!! (Unless you are an experienced advanced linux user who is familiar with changing user ownership of files and directories).
So much work is going into making a detailed installer for all methods that I have a new idea.
I think a new modified installer is in order. One that will detect and configure your system properly with java. I will make a script that will do all the necessary magic. Goodness this is difficult to accomplish. Working out "bugs" currently between scripts for bash1.2, bash2, and ksh. Beta to be posted soon.
This has been updated Oct 19, 2003.
ooooooooooooooooooooooooooooooooooooo

Each Post will be categorialized by installation method in relation to packaging scheme (ie rpm, emerge, tarballs, and deb) Not in that exact order mind you. Let us begin with the RPM enthusiasts out there using Sun's Java VM:
.
</blockquote></center>

**Note**
This portion is for Sun Java VM instructions. Scroll further down for IBM and BlackDown Java VM Installation Instructions.
********

++++++++++++++++++++++++
BEGIN SUN RPM METHOD
++++++++++++++++++++++++

Mandrake Users: remove kaffe first. (rpm -e kaffe --nodeps)
RedHat Users: remove jdkgcj first. (rpm -e jdkgcj --nodeps)

**Note**
These examples are based on installation instructions for Sun's Java VM j2sdk-1.4.0. You will have to substitute my example's path (/usr/java/j2sdk1.4.0) with your installed java VM (/usr/java/j2re1.4.2_05 or equivalent) Instructions on discovering this is mentioned later when needed below.
**End Note**

Download from java.sun.com.

Your package will have the name similiar to this one:

j2sdk1_4_0-fcs-rpm.bin

Execute the file in order to agree and extract the file:

sh j2sdk1_4_0-fcs-rpm.bin
(Substitute j2sdk1_4_0-fcs-rpm.bin with your downloaded file)

This should extract an rpm package like:

j2sdk1-4-0_01.fcs.rpm

Install this like you will install any other rpm:

rpm -Uvh j2sdk1-4-0_01.fcs.rpm
(Substitute j2sdk1-4-0_01.fcs.rpm with your uncompressed file)

Then follow the rest of the instructions to the letter---

Since I had a prior installation I get this when I do:

java -version

<output>
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
</output>

Make the appropriate changes depending on where you installed your java installation whether it be sdk or jre:

The sun package j2sdk-1.4.0-fcs is located :

/usr/java/j2sdk1.4.0

To find out for YOUR particular package, type this command (Please, please, please don't type "or". They are simply there to seperate commandline "options". Which mean use one of the following):

which -b java

or

rpm -ql j2sdk|more

or

rpm -ql j2re|more

and what it says in that first part is what you will have to add to your path statement:

(ie /usr/java/j2sdk1.4.0 in my case.)

You need to add a path statement in your .bash_profile:

**Note**
If you are in a graphical environment using KDE, Gnome, blackbox, and etc, Ignore the vi editor instructions and just type using kate, kwrite, or gedit instead.
**End Note**

(Using vi type:
vi .bash_profile
press "i" (eye) to insert/edit/add the following:)

export JAVA_HOME=/usr/java/j2sdk1.4.0
export PATH=$JAVA_HOME/bin:$PATH

(Hit "Esc" to end editing. Then type:
:wq
to save and quit).

Next type in your terminal or console to activate these changes and use them now in your current session:

souce .bash_profile

Otherwise, you might have to logout then back in to accept these changes.


After doing that, I remove kaffe from my system (Mandrake System) but I have a dependency problem with my wizard packages (Mandrake Control Center). I do this command to keep that program around:

rpm -e kaffe --nodeps

This removes all instances of kaffe binaries from /usr/bin.

**Special Note**
rpm -e jdkgcj --nodeps

for those whom have this package installed on their system (Red Hat Systems).
**End Special Note**

After doing that, I execute the LImeWireLinux.bin installer (do this as a regular user and not root.:

./LimeWireLinux.bin

+++++++++++++++++++++++++
END SUN RPM METHOD
+++++++++++++++++++++++++

nDiScReEt May 11th, 2002 08:01 PM

BlackDown RPM Install
 
+++++++++++++++++++++
BEGIN BLACKDOWN METHOD
+++++++++++++++1+++++

I get this when I do:

java -version

<output>
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.3.1-02b-FCS)
Java HotSpot(TM) Client VM (build Blackdown-1.3.1_02b-FCS, mixed mode)
</output>

Make the appropriate changes depending on where you installed your java installation whether it be sdk or jre:

I put where I downloaded my j2sdk1.3.1-02b-FCS:

/usr/lib/j2sdk1.3.1

You can find your path by typing this command:

which -b java

into my PATH in my .bash_profile:

(Using vi, a linux editor like windows "edit" program, type:

vi .bash_profile

press "i" (eye) to insert/edit/add the following.)


export JAVA_HOME=/usr/lib/j2sdk1.3.1
export PATH=$JAVA_HOME/bin:$PATH

(Hit "Esc" to end editing. Then type:
:wq
to save and quit).

Next type in your terminal or console to activate these changes and use them now in your current session:

souce .bash_profile

Otherwise, you might have to logout then back in to accept these changes.

If you are in a graphical environment using KDE, Gnome, blackbox, etc use kate, kwrite, or gedit instead.

After doing that, I remove kaffe from my system but I have a dependency problem with my wizard packages. I do this command to keep that program around:

rpm -e kaffe --nodeps

This removes all instances of kaffe binaries from /usr/bin.

**Special Note**

rpm -e jdkgcj --nodeps

for those whom have this package installed on their system.
**End Special

I next create soft links to the /usr/bin directory but blackdown has most of all of it's java commands (ie java, javac, etc) as symbolic links. Some people´s configuration will not allow that many symlinks (That is a softlink pointing to another softlink)
the symlinks point to a "hidden" file called .java_wrapper. So I link this to my /usr/bin directory like so:

ln -s /usr/lib/j2sdk1.3.1/bin/.java_wrapper /usr/bin/java

After doing that, I execute the LImeWireLinux.bin installer (do this as a regular user and not root. I don't know a way to install it system wide as root yet without making a script.):

./LimeWireLinux.bin

Installation works. Program installed, running, and functional. I discovered that I had to install the program as user instead of trying to set it systemwide as root.

</snip>

Please let me know by leaving a comment or anything if you have any problems with my solution.

++++++++++++++++++++
END BLACKDOWN METHOD
++++++++++++++++++++

nDiScReEt May 11th, 2002 08:09 PM

IBM Installation
 
Believe it or not, it is the exact mirror of the sun installation steps. I will post changes as they become available to me.

altoine

nDiScReEt May 13th, 2002 01:51 AM

Re: I Have The Solution To All Install Problems
 
+++++++++++++++++++++++++
BEGIN TARBALL INSTALL METHOD
+++++++++++++++++++++++++

I need to add this for those without an rpm java install that is conflicting with another java program or you simply want to get rid of one.

To remove a tarball installed java package (tar.gz and tar.bz2).

First find them all:

which -b java

then remove the directory of the old java tarball path.

rm -fr /usr/local/java/j2sdk1.1.8

Make sure you have appropriate access privileges, but that part should go without saying. So it will be said, nevermore. (What a coincidence, I had just finished reading an edgar allen poe book!)

mkdir /usr/local/java

cd /usr/local/java

Let us assume that you downloaded your java package to the "/temp" directory.

ls /temp

should produce an output like:

j2re1.4.1.tar.gz

unpack the archive from your current directory; /usr/local/java:

tar -xzvpf /temp/j2re1.4.1.tar.gz

Java is now installed and now only needs to be configured to be "seen" by the rest of the system.

like in /etc/profile and ~/.bash_profile:

export JAVA_HOME="/usr/local/java/j2re1.4.1_01/"

Finished.

http://members.fortunecity.com/ndisc...ges/fluor1.jpg


++++++++++++++++++++++
END TARBALL INSTALL METHOD
++++++++++++++++++++++

nDiScReEt May 17th, 2002 11:30 PM

Hopefully A Final Note
 
First, I just wanted to add for those whom have not installed LimeWire yet in their *nix environment that my suggestions were tested in a bash shell and are not guaranteed to work with any other shell environments.

Second, these suggestions that I have provided to fix installation issues are also the best proper way to install LimeWire with a near 100% success rate, which is what my methods are enjoying right now.

Third, I discovered that for anyone using gcc3.1 or higher as their primary and only compiler environement will not be able to install LimeWire using the Linux installer.Unless, you put a proper CLASSPATH into your.bash_profile.

(Do the following:

vi .bash_profile

<press "i" (eye) to begin inserting/editing/adding information>

export CLASSPATH=$CLASSPATH:

<press "Esc" to end editing>

Type the following:

:wq

<This you do to write and quit.>
For those in a graphical environment using KDE, Gnome, blackbox, etc use kate, kwrite, gedit instead.

Use the tarball (tar.gz) instead.

Lastly, feeling confident that this will solve primarily all problems in this forum thread regarding installation issues using a bash environment (I should be a pollitician because I sure know how to cover my @ztsets! LoL), I am marshalling all my time and energies to developing LimeWire from this point onwards. I have my profiles to receive message when anyone leaves a message anywhere I have been and so I will be able to help out even though I physically won't be checking the forums on a daily basis.

Best regards,
altoine

Unregistered May 18th, 2002 12:53 PM

GREAT ! Working

Just wanted to say thanks for posting that here. It did solve my problems installin that app.

After making these changes the installer started and the prog is working.
I use Mandrake 8.2
So you can consider that platform tested and working

nDiScReEt May 18th, 2002 06:01 PM

Quote:

Originally posted by Unregistered
GREAT ! Working

Just wanted to say thanks for posting that here. It did solve my problems installin that app.

After making these changes the installer started and the prog is working.
I use Mandrake 8.2
So you can consider that platform tested and working

Your welcome. :D

altoine

nDiScReEt May 24th, 2002 03:09 PM

Update
 
I am taking a temporary break from modifiying code in LimeWire to make some changes and fixes to the LimeWire Installer. More on this development soon.

andreytcho May 28th, 2002 02:41 PM

works like a charm
 
It seems that all you have to do to get this to work is make the link to you java bin/.java_wrapper

I did it as root and it worked .

ln -s /my_java_location/bin/.java_wrapper /usr/bin/java

Unregistered June 3rd, 2002 09:52 PM

yeah that's all fine and dandy eccept for one thing...

it says i have no vm period now....

a.k.a help!

nDiScReEt June 4th, 2002 01:21 AM

A First!!
 
Quote:

Originally posted by Unregistered
yeah that's all fine and dandy eccept for one thing...

it says i have no vm period now....

a.k.a help!

***Special Note***

Only Blackdown uses .java_wrapper that I am aware of at this time. Any other java vm will not require symlinking this to /usr/bin as java.

****************


1.) How familiar are you with linux console commands? You are saying that when you type this command:

rpm -qa | grep j2

You get no output?

Otherwise, it sounds like a typo somewhere.

If you do get an output, please post it here.

2.) I would like to know if you are using, Sun's, Blackdown's, or IBM's java VM. (This would be answered by your output from Question #1 if you are not certain yourself.

Eagerly awaiting your answers,
Altoine

3.) You are using bash?

If there isn't any typo you might simply have to logout and then back in again to update your path. Otherwise, it will not work before unless you manually type the export commands directly on the command line and not in .bashrc or .bash_profile.

altoine

nDiScReEt June 4th, 2002 01:43 AM

Non-Blackdown Installation Instructions
 
Make the appropriate changes depending on where you installed your java installation whether it be sdk or jre (ie /usr/java/j2sdk1.4.0, /usr/java/j2re1.3.1, /usr/lib/j2re1.3.1, etc):

I put where I downloaded my j2sdk1.3.1-02b-FCS:

/usr/lib/j2sdk1.3.1

into my PATH in my .bash_profile (.bashrc will work, also):

export JAVA_HOME=/usr/lib/j2sdk1.3.1
export PATH=$JAVA_HOME/bin:$PATH

After doing that, I remove kaffe from my system but I have a dependency problem with my wizard packages. I do this command to keep that program around:

(If the above path is added to .bash_profile or .bashrc, you really won't have to remove kaffe if you reboot or logout and then login again before running the LimeWire Installer) This is necessary in order for the path changes can take effect. Depending on your setup, just opening another terminal will not use your new changes. Once the system is using your changes, you will not have to mess with them until you do a java vm upgrade.

Instructions for removing kaffe without breaking anything:

rpm -e kaffe --nodeps

This removes all instances of kaffe binaries from /usr/bin.

**Special Note**
rpm -e jdkgcj --nodeps

for those whom have this package installed on their system.
**End Special Note**


After doing that, I execute the LImeWireLinux.bin installer (do this as a regular user and not root. I don't know a way to install it system wide as root yet without making a script.):

./LimeWireLinux.bin

Installation works. Program installed, running, and functional. I discovered that I had to install the program as user instead of trying to set it systemwide as root.

Helene June 19th, 2002 06:01 AM

Fixed some problems, got a new one
 
Hi,

I did the suggestions, and it fixed my problems in the first run.

I got up a screen asking for shared folder a.s.o.

That worked okey, but when it tried to start the LimeWire application I got up a screen with the limewire logo and a message stating it was loading the gui.

Then the app exited with this error mesage:
./LimeWire: line 1: 1199 Segmentation fault "/home/helene/programs/jre1.3.1_03/bin/java" com.zerog.lax.LAX "/home/helene/programs/LimeWire/./LimeWire.lax" "/tmp/env.properties.1146"

Any ideas?

(I'm running suse professional 7.2)

Helene June 19th, 2002 06:28 AM

Hi again,



I found in another thread this solution that worked for me :)




http://www.gnutellaforums.com/showth...&threadid=7148

Unregistered June 20th, 2002 05:29 PM

nDiScReEt just a quick thanks.

Worked like a charm.

Unregistered June 20th, 2002 05:32 PM

.bash_profile?

Im a newbie.....

where is this and how do i find it?

nDiScReEt June 22nd, 2002 07:01 PM

Quote:

Originally posted by Helene
Hi again,



I found in another thread this solution that worked for me :)




http://www.gnutellaforums.com/showth...&threadid=7148

Thank you. Your problem and solution are both well appreciated. I had came across that solution a long time ago but I had never came across a situation where I needed it implemented. I will add that to the installation guide that I haven't regrettably finished yet. I have a new problem that as far as I have seen on this list, no one has come across it yet. Once, I solve that installation issue, I will indeed have THE ultimate installation and troubleshooting guide.

altoine

nDiScReEt June 22nd, 2002 07:06 PM

Quote:

Originally posted by Unregistered
.bash_profile?

Im a newbie.....

where is this and how do i find it?

it is in your home directory of your user.

(example:

suppose your user login name is yesm

/home/yesm/.bash_profile)

If you don't have .bash_profile .bashrc is a good substitute.

any file with a "." (period) before the name of the file or directory means that it is "hidden". Doing a "ls" or "ls -l" will not find the file. While "ls -a" or "ls -a .bash*" will!

altoine

Unregistered June 27th, 2002 09:50 AM

Add me to the list of Linux LimeWire "L-users"

I have read all the threads in this session and have followed the instructions, but to date I still haven't seen any improvement in the install. In short, LimeWire still cannnot find the PATH to my Java virtual machine.

Here are my specs:
I have this installation path for my java:
/usr/java/j2re1.4.0_01

I have created a symbolic link to:
/usr/bin/java
with this server path:
/usr/lib/j2re1.4.0_01/bin/.java_wrapper

The symbolic link was created, so the directory path seems to be valid.

I have edited my .bash_profile to read:
export Java_HOME=/usr/java/j2re1.4.0._01
export PATH=$JAVA_HOME/bin:$PATH

After making these updates, I log out as root and then type:
sh ./LimeWireLinux.bin and receive the missing virtual path error.

So, I'm not sure how to proceed from here. Any clues?

nDiScReEt July 1st, 2002 12:37 AM

Excuse the Delay in Replying
 
Quote:

Originally posted by Unregistered
Add me to the list of Linux LimeWire "L-users"
...
I have created a symbolic link to:
/usr/bin/java
with this server path:
/usr/lib/j2re1.4.0_01/bin/.java_wrapper

The symbolic link was created, so the directory path seems to be valid.

That depends... the link can be broken as it should be in your case. You only need to create a link to /usr/bin/java with .java_wrapper ONLY if it is a jvm from www.blackdown.org.
Your version seems to be a different sort. under your java bin directory should be a java, javac, etc that you can link to the /usr/bin directory :

ln -s /usr/lib/j2re1.4.0/bin/java /usr/bin/java

and

ln -s /usr/lib/j2re1.4.0/bin/javac /usr/bin/javac


I have edited my .bash_profile to read:
export Java_HOME=/usr/java/j2re1.4.0._01
export PATH=$JAVA_HOME/bin:$PATH
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
All wrong above. Close but not for *nix useage. It should read:

export JAVA_HOME=/usr/lib/j2re1.4.0
export PATH=$JAVA_HOME/bin:$PATH

or

export JAVA_HOME=/usr/lib/j2re1.4.0_01
export PATH=$JAVA_HOME/bin:$PATH

depending on the actual path to your jvm directory. You have it listed as /usr/lib/j2re1.4.0 in one instance and then have the path listed as j2re1.4.0_01 in another. Everything is predominately case sensitive in *nix (linux, unix, freebsd, etc).
This should fix your problem and I will update/upload the Installation Instructions on how to install using any environment and any jvm from virtually any source. My apologies for not doing this sooner but I was away for a few weeks. Deep in rebuilding my own projects from the ground up.

altoine

OTazman July 31st, 2002 01:39 PM

just help me super newbie to linux
 
I have Redhat 7.3 with j2re-1.4.1-beta i did everything exactly like it was told, and I still get the:
""Preparing to install...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
No Java virtual machine could be found from your PATH
environment variable. You must install a VM prior to
running this program. "" error message what do I do?


Thanks in Advance,
Sean Dolan

nDiScReEt July 31st, 2002 11:47 PM

Re: just help me super newbie to linux
 
Quote:

Originally posted by OTazman
I have Redhat 7.3 with j2re-1.4.1-beta i did everything exactly like it was told, and I still get the:
""Preparing to install...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
No Java virtual machine could be found from your PATH
environment variable. You must install a VM prior to
running this program. "" error message what do I do?


Thanks in Advance,
Sean Dolan

[SIZE=1][FONT=arial][FONT=arial][FONT=arial][FONT=arial]

export JAVA_HOME=/usr/java/j2re1.4.0_01
export PATH=$JAVA_HOME/bin:$PATH

Is /usr/java/j2re1.4.0_01 really the path to your java version?

To test type:

which java

Do you get any output?
If you get output, that should be what goes after JAVA_HOME.
In the second export command (PATH), is JAVA_HOME referenced as #JAVA_HOME or JAVA_HOME as the $, dollar sign, is needed in the second export line not the first.
In the second line, is $JAVA_HOME/bin followed directly by $PATH with no :, colon, or is it followed with a :, colon ($JAVA_HOME/bin:$PATH)?
It needs to be followed by a :, colon.

Did you make sure that when you exported JAVA_HOME, you made sure the cases matched? (As it is case sensitive --for the newbies)

I postulate that one of the above questions will answer and solve your problem.

OTazman August 1st, 2002 05:52 AM

Ok this is what i get...
 
after doing that which java i get this:


[root@dhcp-58-42 Downloads]# which java
/usr/bin/which: no java in (/usr/local/sbin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/root/bin)

so now what?

thanks in advance,
SED

OTazman August 1st, 2002 05:55 AM

oh and just to let you know....
 
i reinstalled RH 7.3 cuz I had a prob with my video card, I also installed j2re 1.4 this time instead of j2re 1.4 beta, and another thing, I'm doing all of this in 'root' could that be the problem? Sorry I'm a Super Newbie =)


thanks -SED

OTazman August 1st, 2002 07:09 AM

I GOT IT WERKIN' THX FOR ALL THE HELP!
 
The export command wasn't working prolly cuz I was doing it wrong, so I did a 'vi' command on the .bash_profile and tried to edit it that way but I didn't know any of the commands, so I opened the .bash_profile in 'KATE' (advanced text editor) anyways I added the export commands under the other export command that was already there, and saved it logged in and out did a 'which java' command and bodda bing bodda boom it was there, I also did a 'java -version' command and that also worked too, so I was very delighted, so I did the 'sh' command on the LimeWireLinux.bin and it installed it with some errors that didn't seem to effect the installation process... hmmm.. ok so just wanted you to stop boggling your minds thanks for the help =)


-peace SED

nDiScReEt August 1st, 2002 09:05 AM

Re: I GOT IT WERKIN' THX FOR ALL THE HELP!
 
Quote:

Originally posted by OTazman
The export command wasn't working prolly cuz I was doing it wrong, so I did a 'vi' command on the .bash_profile and tried to edit it that way but I didn't know any of the commands, so I opened the .bash_profile in 'KATE' (advanced text editor) anyways I added the export commands under the other export command that was already there, and saved it logged in and out did a 'which java' command and bodda bing bodda boom it was there, I also did a 'java -version' command and that also worked too, so I was very delighted, so I did the 'sh' command on the LimeWireLinux.bin and it installed it with some errors that didn't seem to effect the installation process... hmmm.. ok so just wanted you to stop boggling your minds thanks for the help =)


-peace SED

[COLOR=skyblue][COLOR=skyblue][COLOR=skyblue][COLOR=skyblue][COLOR=skyblue][COLOR=skyblue]

Congratulations! No boggle at all as I told you the problem was more likely a typo which apparently it was. There is no way you can enter the export command correctly and not be able to do "which java" or "java -version". I thank you for opening me to another level of newbie instruction. I see I will have to explain all the way to the detail of what editor and with how to save and exit. Thank you once again and congratulations. If the second line of the "export JAVA_HOME" in your ".bash_profile is correct, you can remove the line above it as it is wasting space.

altoine:D

Unregistered August 14th, 2002 11:11 AM

Bingo!
 
Thanks!

This worked. The solution needs to be posted on the Limewire website.

Lindsay Haisley
fmouse@fmp.com

Unregistered August 29th, 2002 09:40 AM

Thanks
 
Thanks for the install help. This guide also allowed me to install java completely which my RedHat 7.3 won't allow.

nDiScReEt August 29th, 2002 02:24 PM

Your Welcome
 
Quote:

Originally posted by Unregistered
Thanks for the install help. This guide also allowed me to install java completely which my RedHat 7.3 won't allow.
The instructions as far as using $JAVA_HOME in your .bash_profile or .bashrc has been what had to be done for all java installed on unix but it isn't in the installer to do this. Probably because some admins limit what shells their users can use and sometimes will disable bash outright. When using a different shell like ksh (Korn shell), your export command is different. An entirely different syntax. I was going to create instructions for the other shells, but it appears no one has had any situations with an account with the restriction to use bash (Bourne Again shell). I have a script to do all the installing using LimeWire's tarball or installer with specific java packages. I want it to be able to use any java installer and thus I will have to get back to my little script one day and revise it with the necessary changes to bring that capability to fruition.

altoine

Unregistered September 10th, 2002 08:42 PM

Thank you nDiScReEt for the time that you have spent preparing this little tut. You have solved all my problems, and I am very thankful. :)

/NaRdS

vbp6us September 24th, 2002 06:28 PM

Which one do i download?

ftp://ftp.tux.org/pub/java/JDK-1.3.1


Im running Suse 8.0

nDiScReEt September 28th, 2002 02:58 PM

Quote:

Originally posted by vbp6us
Which one do i download?

ftp://ftp.tux.org/pub/java/JDK-1.3.1


Im running Suse 8.0

That depends on if you plan on doing development with java or not. If all you want to do is use java supported and ran programs, download the jre. If you are like me and do development with creating programs that run and use java, use the sdk. Since tux.org is a popular download site and you might find yourself waiting to get a turn on the server since it limits it's users to a maximum of 100 at any one time.

ftp://metalab.unc.edu/pub/linux/deve.../i386/FCS-02b/

Be sure to follow the install guides for which ever one you choose (jre or sdk).
So that your browsers will use the latest java version on your system. I personally recommend using the jdk-1.4.1 versions as the latest limewire 2.5.5 and up utilize added features provided by java 1.4.1 that isn't present in java 1.3.1.

Here is the link for that one:

ftp://metalab.unc.edu/pub/linux/deve...4.1/i386/beta/

altoine

P.S. I also recommend that everyone use the sdk over the jre as you don't ever know when there is a source file for a java program that was custom made for you by a "friend" on the net and all you need to do is compile the program.

altoine

Unregistered October 3rd, 2002 08:09 PM

For those who are running Debian, this might help.

My system is running Debian unstable, with a freshly installed copy of J2SDK 1.4.1.

The install ran perfectly for me after I ran the following:
ln -s libstdc++-libc6.2-2.so.3 libstdc++-libc6.1-1.so.2


Regards,


Rex

nDiScReEt October 4th, 2002 11:06 AM

Quote:

Originally posted by Unregistered
For those who are running Debian, this might help.

My system is running Debian unstable, with a freshly installed copy of J2SDK 1.4.1.

The install ran perfectly for me after I ran the following:
ln -s libstdc++-libc6.2-2.so.3 libstdc++-libc6.1-1.so.2


Regards,


Rex

That is certainly something to look into Rex as that is highly unrelated to a problem with LimeWire in general but a definitely problem for users of Suse for many other java-based applications.

altoine

Unregistered October 11th, 2002 03:34 AM

launching after install
 
i am running mandrake 9.0
i got limewire to install after a fair bit of work. my problem is a rather cosmetic one
there is no executeable program to launch limewire.
i can get the program to run - and it works fine - by typing ./runLime.sh in the LimeWire directory from a console window
i tried to add a menu entry so i could launch from my menu instead of opening a terminal and typing it everytime
using menudrake i made the menu entry with the launch command...
/home/darc/LimeWire/./runLime.sh
however it keeps giving me the error that it cannot find the program -- because the launcher is a shell script, i am assuming that the menu is looking for an executable
i tried making a symlink -- that didnt work either
any ideas how i can get limewire to launch from the menu ??
thanks
P.S - the ./runLime.sh command is the only one that will launch the program --
LimeWire -- or any others that i have tried that are supposed to work will not launch it either

nDiScReEt October 13th, 2002 01:47 AM

Re: launching after install
 
Quote:

Originally posted by Unregistered
i am running mandrake 9.0
i got limewire to install after a fair bit of work. my problem is a rather cosmetic one
there is no executeable program to launch limewire.
i can get the program to run - and it works fine - by typing ./runLime.sh in the LimeWire directory from a console window
i tried to add a menu entry so i could launch from my menu instead of opening a terminal and typing it everytime
using menudrake i made the menu entry with the launch command...
/home/darc/LimeWire/./runLime.sh
however it keeps giving me the error that it cannot find the program -- because the launcher is a shell script, i am assuming that the menu is looking for an executable
i tried making a symlink -- that didnt work either
any ideas how i can get limewire to launch from the menu ??
thanks
P.S - the ./runLime.sh command is the only one that will launch the program --
LimeWire -- or any others that i have tried that are supposed to work will not launch it either

This is an easy thing to create.

My instructions (always) will require the use of a terminal or console. I am explaining this for your benefit and more for the many newbies.

let us use "vi" since that type of editor is normally on a majority of *nix operating systems.

type:

vi LimeTime

(You can substitute "LimeTime" for any other name that you prefer that won't conflict with any pre-existing programs)

press:

i

to enable insert mode.

type all that follows:

#/bin/sh
sh $HOME/LimeWire/runLime.sh

(Substitute the path for your chosen absolute path to your installed LimeWire directory)

press:

Esc

to end your editing/insert mode.

type:

:wq

to save/write and quit.

type:

chmod +x LimeTime

(Again substitute "LimeTime" for your preferred executable name)

Test it by typing:

LimeTime

Your program should work without any hitch provided you run it from your home directory.

There are other ways to create an executable using other commands but that will be discussed at a later time when the need arises for now.

I hope this is helpful for you.

altoine

Unregistered October 13th, 2002 06:33 PM

I tried what you said --
using vi i typed
#/bin/sh
sh $HOME/LimeWire/runLime.sh

then did

chmod +x LimeTime --( even used that file name lol )

this was the output when i tried to run it --- yes i was in the right directory

Exception in thread "main" java.util.zip.ZipException: No such file or directory
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:112)
at java.util.jar.JarFile.<init>(JarFile.java:117)
at java.util.jar.JarFile.<init>(JarFile.java:55)

any ideas ???
thanks

fmouse October 13th, 2002 09:41 PM

Quote:

Originally posted by Unregistered
For those who are running Debian, this might help.

My system is running Debian unstable, with a freshly installed copy of J2SDK 1.4.1.

The install ran perfectly for me after I ran the following:
ln -s libstdc++-libc6.2-2.so.3 libstdc++-libc6.1-1.so.2


Regards,


Rex

This is also a problem with Debian Woody. It's worth noting that on woody, at least, libstdc++-libc6.2-2.so.3 is itself a symlink to libstdc++-3-libc6.2-2-2.10.0.so, so a better command, albeit possibly not as version-independent, would be

ln -s libstdc++-3-libc6.2-2-2.10.0.so libstdc++-libc6.1-1.so.2

And it should be noted, for people with possibly less experience, that either command should be preceeded by

cd /usr/lib

BTW, thanks so much for this! Getting limewire installed and running remotely for my son on his Linux box (he's in Maine, I'm in Texas) has been a PITA, but it looks like we're in the clear now!

Unregistered October 14th, 2002 09:26 AM

my previous message


I tried what you said --
using vi i typed
#/bin/sh
sh $HOME/LimeWire/runLime.sh

then did

chmod +x LimeTime --( even used that file name lol )

this was the output when i tried to run it --- yes i was in the right directory

Exception in thread "main" java.util.zip.ZipException: No such file or directory
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:112)
at java.util.jar.JarFile.<init>(JarFile.java:117)
at java.util.jar.JarFile.<init>(JarFile.java:55)

any ideas ???
thanks
-----------------------------
no need to repsond.. i figured it out
i did a classpath statement -- just because i happened to come accross a java class error during this process.... and voila everything works perfect now... not only can i run limewire from the konsole... i can now launch it from a desktop icon...

thanks for the help

Unregistered October 14th, 2002 12:11 PM

Re: A First!!
 
Quote:

Originally posted by nDiScReEt


***Special Note***

Only Blackdown uses .java_wrapper that I am aware of at this time. Any other java vm will not require symlinking this to /usr/bin as java.

****************


1.) How familiar are you with linux console commands? You are saying that when you type this command:

rpm -qa | grep j2

You get no output?

Otherwise, it sounds like a typo somewhere.

If you do get an output, please post it here.

2.) I would like to know if you are using, Sun's, Blackdown's, or IBM's java VM. (This would be answered by your output from Question #1 if you are not certain yourself.

Eagerly awaiting your answers,
Altoine

3.) You are using bash?

If there isn't any typo you might simply have to logout and then back in again to update your path. Otherwise, it will not work before unless you manually type the export commands directly on the command line and not in .bashrc or .bash_profile.

altoine


Unregistered October 14th, 2002 12:15 PM

Re: A First!!
 
Quote:

Originally posted by nDiScReEt


***Special Note***

Only Blackdown uses .java_wrapper that I am aware of at this time. Any other java vm will not require symlinking this to /usr/bin as java.

****************


1.) How familiar are you with linux console commands? You are saying that when you type this command:

rpm -qa | grep j2

You get no output?

Otherwise, it sounds like a typo somewhere.

If you do get an output, please post it here.

2.) I would like to know if you are using, Sun's, Blackdown's, or IBM's java VM. (This would be answered by your output from Question #1 if you are not certain yourself.

Eagerly awaiting your answers,
Altoine

3.) You are using bash?

If there isn't any typo you might simply have to logout and then back in again to update your path. Otherwise, it will not work before unless you manually type the export commands directly on the command line and not in .bashrc or .bash_profile.

altoine


HELLO ALL
I AM A NEWBIE TO LINUX HOWEVER, I THOUGHT YOU HAD TO UPDATE YOUR PATH NO MATER WHATVERSION OF REDHAT YOU ARE USEING.

I HAVE JUST INSTALLED REDHAT 8.0(KIXKS A$$) AND I HAVE TRIED TO INSTALL LIMEWIRE AND GET THE SAME ERRORS AS EVERYONE ELSE. WHEN YOU SAY EDIT THE BASH PROFILE DO YOU MEAT THE /ETC/PROFILE FILE?? I HAVE TRIED TO INSTALL THIS APP AS ROOT. I ALSO INSTALLED THE JAVA VM AS ROOT AS WELL. AM I DOING SOMETHING WRONG??"

Unregistered October 14th, 2002 04:54 PM

Re: I Have The Solution To All Install Problems
 
Quote:

Originally posted by nDiScReEt
<center>
<blockquote>
ooooooooooooooooooooooooooooooooooooo
0 NOTE 0
ooooooooooooooooooooooooooooooooooooo
This is 100% guaranteed to work in a Bourne Again shell environment (bash or sh). Other shell solutions to be posted shortly.
So much work is going into making a detailed installer for all methods that I have a new idea.
I think a new modified installer is in order. I will make a script that will do all the necessary magic with the LimeWireLinux.tgz tarballs and possibly the RPM packages.
This has been updated Aug 16, 2002.
ooooooooooooooooooooooooooooooooooooo

Each Post will be categorialized by installation method in relation to packaging scheme (ie rpm, emerge, tarballs, and deb) Not in that exact order mind you. Let us begin with the RPM enthusiasts out there using blackdown:
.

</blockquote></center>
I had posted to these forums a solution to everyones' ails (no complaints or disagreements so far) and I will repost my solution to this thread.

<snip>

**Note**
This portion is for blackdown java vm instructions. Scroll further down for other instructions for IBM and Sun.
********

I get this when I do:

java -version

<output>
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.3.1-02b-FCS)
Java HotSpot(TM) Client VM (build Blackdown-1.3.1_02b-FCS, mixed mode)
</output>

Make the appropriate changes depending on where you installed your java installation whether it be sdk or jre:

I put where I downloaded my j2sdk1.3.1-02b-FCS:

/usr/lib/j2sdk1.3.1

You can find your path by typing this command:

which -b java

into my PATH in my .bash_profile:

(Using vi, a linux editor like windows "edit" program, type:

vi .bash_profile

press "i" (eye) to insert/edit/add the following.)


export JAVA_HOME=/usr/lib/j2sdk1.3.1
export PATH=$JAVA_HOME/bin:$PATH

(Hit "Esc" to end editing. Then type:
:wq
to save and quit).

If you are in a graphical environment using KDE, Gnome, blackbox, etc use kate, kwrite, or gedit instead.

After doing that, I remove kaffe from my system but I have a dependency problem with my wizard packages. I do this command to keep that program around:

rpm -e kaffe --nodeps

This removes all instances of kaffe binaries from /usr/bin.

I next create soft links to the /usr/bin directory but blackdown has most of all of it's java commands (ie java, javac, etc) as symbolic links. Some people´s configuration will not allow that many symlinks (That is a softlink pointing to another softlink)
the symlinks point to a "hidden" file called .java_wrapper. So I link this to my /usr/bin directory like so:

ln -s /usr/lib/j2sdk1.3.1/bin/.java_wrapper /usr/bin/java

After doing that, I execute the LImeWireLinux.bin installer (do this as a regular user and not root. I don't know a way to install it system wide as root yet without making a script.):

./LimeWireLinux.bin

Installation works. Program installed, running, and functional. I discovered that I had to install the program as user instead of trying to set it systemwide as root.

</snip>

Please let me know by leaving a comment or anything if you have any problems or success with my solution.


From: Anthos


After reading your solution to the prob. installing LimeWire I finally got the installer to work:

I then tried running the prog. And got this error message:

[root@xeio] LimeWire]# sh runLime.sh
/usr/java/jre1.3.1_05/bin/i386/native_threads/java: relocation error: /usr/java/ jre1.3.1_05/lib/i386/libpreemptive_close.so: symbol __libc_sendto, version GLIBC _2.0 not defined in file libc.so.6 with link time reference

Have any Sugstns ??
I really appreciate your help

nDiScReEt October 20th, 2002 12:38 PM

Re: Re: I Have The Solution To All Install Problems
 
Quote:

Originally posted by Unregistered



From: Anthos


After reading your solution to the prob. installing LimeWire I finally got the installer to work:

I then tried running the prog. And got this error message:

[root@xeio] LimeWire]# sh runLime.sh
/usr/java/jre1.3.1_05/bin/i386/native_threads/java: relocation error: /usr/java/ jre1.3.1_05/lib/i386/libpreemptive_close.so: symbol __libc_sendto, version GLIBC _2.0 not defined in file libc.so.6 with link time reference

Have any Sugstns ??
I really appreciate your help

Try this on the commandline (you more than likely will have to be root.

altoine

Unregistered October 24th, 2002 11:55 PM

Can't find libc.so.6
 
I run SuSE 8.1
When I try to run the installer "sh ./LimeWireLinux.bin" it starts and then complains that it cannot find libc.so.6 although i have the file. I probably need to do a symlink somewhere. Anybody knows where and under what name?

Tony

nDiScReEt October 26th, 2002 12:38 PM

Quote:

Originally posted by Unregistered
For those who are running Debian, this might help.

My system is running Debian unstable, with a freshly installed copy of J2SDK 1.4.1.

The install ran perfectly for me after I ran the following:
ln -s libstdc++-libc6.2-2.so.3 libstdc++-libc6.1-1.so.2


Regards,


Rex

Rex forgot to mention that you would have to create that link in the actual directory where libstdc++-libc6.2-2.so.3 is located. What Rex is doing is providing a link to the old libc6.1-1.so.2 as that is no longer seen libstdc++2.10-2.96-0.80mdk for my mandrake package which is actually symlinked to /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so.

To find out where your libstdc++-3-libc6.2-2-2.10.0.so is located type this command:

whereis libstdc++-3-libc6.2-2-2.10.0.so

find that and then symlink it like this to keep symlinks to a minimum (ie to avoide a symlink to a symlink that is symlinked to an actual file) follow these instructions;

First, go to the directory where the whereis program located your file and then type:

ls -l libstdc++*

we type this command to check to see if the symlink:

libstdc++-libc6.2-2.so.2

isn't already present. If it isn't then create the symlink:

ln -s libstdc++-3-libc6.2-2-2.10.0.so libstdc++-libc6.2-2.so.2


Thank you Rex for posting the solution to the Suse 8.1 runtime issue with glibc-type error messages when trying to execute limewire after a successful install, as I couldn't since I had to remove Suse 8.1 to reconfigure my development box.

altoine

SolarWinds October 29th, 2002 10:07 PM

You Da Man!!

Unregistered November 12th, 2002 04:17 PM

Your solution does not work
 
I type
java -version
<output>
bash: java: command not found

I type
which -b java
<output>
type: usage: type [-apt] name [name ...]


I type ./LimeWireLinux.bin
<output>
Preparing to install...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
No Java virtual machine could be found from your PATH
environment variable. You must install a VM prior to
running this program.


Yes Java is installed I installed j2re then j2sdk incase I missed something, sucsessful Java Install but there is no obvious way to tell just no errors therefore good.

jameswilson@roadrunner.nf.net

nDiScReEt November 14th, 2002 07:18 AM

Re: Your solution does not work
 
Quote:

Originally posted by Unregistered
I type
java -version
<output>
bash: java: command not found

I type
which -b java
<output>
type: usage: type [-apt] name [name ...]

That is why the command:

which java

is so beautiful! It means that java isn't properly configured on your system. Definitely when you type this command:

java -version

and don't get tthe apropriate response.

Let us try to help you out here. Let me use the more recent java package to run you through the install process...


1) I go to java.sun.com and get the latest java package: j2se 1.4.1.

2) I next download it to my home directory.

3) I make the package executable if it isn't like this:

chmod +x j2sdk-1_4_1_01-linux-i586-rpm.bin

4) I next execute the package:

sh j2sdk-1_4_1_01-linux-i586-rpm.bin

5) I agree to the licensing terms.

6) I am left with:

j2sdk-1_4_1_01-fcs-linux-i586.rpm

I install this as root:

rpm -Uvh j2sdk-1_4_1_01-fcs-linux-i586.rpm

7) Make sure it is installed by typing this command:

java -version


This should output:

java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)

8) Now, that linux has java installed and running. We are left with configuring linux for java development/limewire installation.

9) Find where java is installed on your system with this command:

which java

You should have this exact output:

/usr/java/j2sdk1.4.1_01/bin/java

10) edit your .bash_profile (or .bashrc if your system doesn't come with .bash_profile) and add these lines to this file:

export JAVA_HOME=/usr/java/j2sdk1.4.1_01
export PATH=$JAVA_HOME/bin:$PATH
export CLASSPATH=$CLASSPATH:

***SPECIAL NOTE***
Make sure that you don't forget the period (.) at the beginning of your file as this denotes your file as a hidden file, which what .bash_profile and .bashrc are!

Type:

ls .bash*

to verify what you have on your system.

********************

11) Then we activate these changes with the following command:

source .bash_profile

or simply logout and then back in if you prefer the M$ way of doing things.

12) Install LimeWire as instructed to do so as a regular user.

Otherwise, this link might help:

http://www.gnutellaforums.com/showth...9810#post59810

altoine

Unregistered November 18th, 2002 07:01 AM

jdkgcj rpm real culprit?
 
I have had install problems with Limewire on Red Hat 8.0 that are exactly like those described by others in this forum. I have tried both the Sun 1.4 SDK and the Sun 1.4 jre. I could not get Limewire to install on either even though I would get the following output when running the 'java -version' command:

java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)

When I ran a 'which java' command, it came back with /usr/bin/java instead of /usr/java/j2re1.4.1_01/bin/java.

rpm -q --whatprovides /usr/bin/java pointed to the jdkgcj rpm.

rpm -e --nodeps jdkgcj and voila! Installs like a charm.

Herb

nDiScReEt November 18th, 2002 08:56 AM

Thank you, Herb! I knew that it was a java program that was causing the problem but didn't similiar problems as I do an Expert installation everytime and choose all my packages by hand.
I will definitely have to update and include that feature in the howto. Is this ok with you, Herb?

altoine


All times are GMT -7. The time now is 10:42 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.

Copyright © 2020 Gnutella Forums.
All Rights Reserved.