Mercury giving a wierd Java error.

WhiskeyTangoFoxtrot · 05-13-2006, 06:08 PM

g'day
i installed java completely using the tutorial on http://stanton-finley.net/fedora_cor...ion_notes.html and i know it works as i can run azureus perfectly. when i try to run mercury build 1711-B6 it gives me the output

Code:

bash-3.1$ mercury
awk: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/bin/ls: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/jre1.5.0_06/bin/java: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory

i have installed using the rpm and it apparently works on my friends FC5 but not mine. any suggestions ?

Hungry ghost · 05-13-2006, 06:31 PM

It's because NPTL; take a look at this.

WhiskeyTangoFoxtrot · 05-22-2006, 07:34 PM

sorry mate but i have no clue what they are talking abt :consused: . ok so this NPTL thing is causing some trouble but they say we should download a Setup.bin file and install manualy from that, i cant even find a bin file on the download page.
i was wondering if its possible to shut off this NPTL thing, reason im saying this is because if this is the problem then my other friend already running FC5 must have it switched off ( he has no clue abt NPTL so i doubt he has done it himself )

WhiskeyTangoFoxtrot · 05-22-2006, 07:40 PM

hmm.....i saw your post on the mercury forums and now it makes some sense. but does this mean one will have to use version 1709 and not the recent ones ( 1710 or the latest betas of 1711 ) which are rpm's ?

WhiskeyTangoFoxtrot · 05-22-2006, 07:49 PM

well, i got the bin file for 1709 and tried to run it after changing the permissions. this is what the terminal coughed up :

Code:

[root@localhost Desktop]# ./*.bin
Preparing to install...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
awk: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/bin/ls: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory

Launching installer...

grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/jre1.5.0_06/bin/java: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory

looks just like the error i was getting from the executable from the rpm installer. could it be that i have some files missing or something ? i have a pretty much standard FC5 installation.

Hungry ghost · 05-22-2006, 07:49 PM

Hi, I think you can't use the rpm's nor the 1709 installer with NPTL enabled, so you must go to the mercury forum's 'Latest Beta Release' section and download the latest update file (currently 1711 B08). Then, you must uncompress it somewhere (/usr/share/mercury or /usr/lib/mercury should be ok). To run Mercury you must go to your /mercury/installation/path/, cd to the 'startup' directory and execute the startup_linux.sh script. It's a bit annoying to do it all the time but it works.

Hope it works for you.

Edit: I think you could use the .rpm file if you go to /usr/lib/mercury/startup and execute the startup_linux.sh script.

WhiskeyTangoFoxtrot · 05-23-2006, 12:08 AM

well, your suggestion worked

i used the startup_linux.sh script of the rpm and got mercury working however i need to keep the console open in order to keep the programme running. well, now i have to figure out why its missbehaving like this on my comp while my roommate is able to run it perfectly on his laptop using the same kernel as me ( not to mention same distro )

thanxs

Hungry ghost · 05-23-2006, 04:02 PM

Have you tried the following?:

Code:

./startup_linux.sh &

After that you should be able to press enter in the command line and then exit.

WhiskeyTangoFoxtrot · 05-24-2006, 10:13 PM

well, pressing enter did free up that terminal but mercury is still linked to it and closes when i close the console. is it possible to run mercury using a shortcut or something ? if so, what would i put down as the command for the shortcut ?

Hungry ghost · 05-25-2006, 09:37 AM

After running startup_linux.sh & you must press 'enter' in the command line, then type exit (instead of just closing the terminal from the window 'x' button) and then press 'enter' again. With this, mercury should get dettached and you won't have the terminal running.

As for the shortcut, I trid making a symbolic link in '/usr/bin' to the startup script but it didn't work for me (I got some errors when running the symbolic link). Anyway, if you just click on the startup script from the GUI, mercury will run.