(08-09-2010, 02:09 PM)DeadManWalking Wrote: [ -> ]the bin64 (linux) does not work (start) for me.
Not on double clicking the marked executeable, not in terminal.
(I know how to start BIN-files, but wth are bin64 files? I tried it my way..)
Terminaloutput:
Quote:mark@mark-desktop:~/Desktop/RendererFeatTest64$ sudo chmod +x RendererFeatTest.bin64
mark@mark-desktop:~/Desktop/RendererFeatTest64$ sudo sh ./RendererFeatTest.bin64./RendererFeatTest.bin64: 1: ELF: not found
./RendererFeatTest.bin64: 1: Syntax error: Unterminated quoted string
mark@mark-desktop:~/Desktop/RendererFeatTest64$ sudo sh ./RendererFeatTest.bin
sh: Can't open ./RendererFeatTest.bin
mark@mark-desktop:~/Desktop/RendererFeatTest64$ sudo ./RendererFeatTest.bin64
./RendererFeatTest.bin64: error while loading shared libraries: libGLEW.so.1.5: cannot open shared object file: No such file or directory
The last command you listed was correct (but you don't need to use sudo in this case and would actually recommend not doing so).
From the error you get it seems you are missing at least one of the shared libraries.
It would help to know what distro you are using and if you are using the 32 or 64bit version of your OS (if you are using a 32bit OS you need to use the 32bit executable).
I'm pretty sure using:
ldd ./RendererFeatTest.bin | grep found
when navigated to the correct directory (~/Desktop/RendererFeatTest64) should give you a list of missing libraries.
If they're part of a pack then it shouldn't be to hard to get.
Hope this helps somewhat.
I'm using Ubuntu 10.04 Lucid 64 bit.
Well, the term asks after a "libGLEW.so.1.5" ... in the 64libs folder is a libGLEW.so.1.5.1 , but not a 1.5 .....
That is really odd, you are the second user with this same issue (different distros though).. Those files are in the ZIP archive as symbolic links.. Did you extract it to a file system with no symlink support? What program did you use to extract the zip?
I think I figured it out.. file-roller has a bug.. If I use file-roller (gnome) and DRAG the folder into another nautilus window, it fails to recreate the symlinks.. hmm. even if I use the extract option it fails.. Oh, but if I use the extract option and specify ALL files it correctly creates the symlinks... This is especially odd since I USED file-roller to create those zips. Time to report a bug
@Urkle:
I ran into similar issues as Deathmanwalking as it seems to me, or ?
Have a look here:
http://www.frictionalgames.com/forum/thr...l#pid30219
I had similar problems under arch64 as well as under Ubuntu 9.04 x64.
May I ask you to do a ls -la in your correctly installed graphics compatibility app and post the output here ?
TIA,
D$
Thanks for your quick reply !
I will cross check this with my both installations (Ubuntu and arch64). I guess some newly correct set symlinks will fix my missing libs issues
Just a quick question:
Why were you using symlinks inside your own lib folder ?
I normally use symlinks to libs rather to fix issues with games relying on older libs (mostly other name).
(08-13-2010, 11:04 PM)Urkle Wrote: [ -> ]Here is the ls-lR output
...
(08-13-2010, 11:28 PM)Darksoul Wrote: [ -> ]Just a quick question:
Why were you using symlinks inside your own lib folder ?
I normally use symlinks to libs rather to fix issues with games relying on older libs (mostly other name).
I just copied over the libs from my build environment as is, instead of renaming them to the "linked" name.
I've made a script to rename the libs to their linked name so I don't have to deal with symlinks in the future.