libSDL errors on 64 bit linux systems

as explained in another part of the forum, people getting libSDL errors should copy the relevant 32 bit libSDL file into the libs folder of Secondlife,

however i was wondering if the relevant lib files required could be bundled into the package to save the less knowledgable linux users (like myself) frustratingly having to resort to long trauls through forums and search engines to find the solution.

is there a legal issue with doing so? or could you offer a 64-bit linux users a seperate secondlife client? or even just supply the relevant libs as a seperate download for 64-bit users?

i think it'd be really useful to be able to get all the relevant files from one place for us n00by linux'ers


Cheers

Stewart

It'd probably be best to get the distribution specific 32bit copies of libuuid and libSDL to fix these. There may or may not be differences in these files between distributions that may or may not cause errors. It'd be another variable in testing. Not that running a 64 bit unaware program isn't a possible risk in itself but that should be a lesser problem as to mixing distro libraries.

i see.

so whats the easiest method of obtaining these libs?

personally i use Kubuntu, but searching for the specific libs in the adept package manager doesnt come up with any joy. i read that i can get the sdl libs from the main sdl website, but i have no idea what i'm doing.

is there a specific repository where i can get it? or is that a dangerous idea as i dont want to be installing 32-bit libs on the main system.

or do i need to get the development package and compile my own?


cheers for any help you can give me.

Stewart

http://packages.ubuntu.com/

It should let you search your release going back quite a long time. I think most people are on Dapper and probably some will be switching to Edgy in the next few months. Make a note, when adding these libraries for SL put them in secondlife/lib and not your system.

The only two files currently needed for 64 bit users are libuuid and libSDL.

I found the 32 bit libSDL in my previous Secondlife/lib folder.

yeah i'm pretty sure i had the libs in a previous version... i'm wishing i kept it instead of simply replacing the folder with the new version.

thanks for all the info, i'll take a look.

Strange. I haven't installed those 32-bit libraries, and everything seems to be working fine for me (Fedora Core 5 on an Athlon 64 4000+; and YES with the 64-bit version of the OS installed). I honestly haven't paid attention to stdout/stderr messages or logs though. Are you worried about something there, or will SL actually not start up for you at all?

Debian/Ubuntu are full 64 bit, RedHat has not converted to full 64 bit in all libraries, however they are 64 bit compatible but will use 32 bit libraries. SL does not accept a 64 bit library header even though the library would work fine (in theory).

Interesting... 64bit Fedore Core 5 on an AMD 64bit proc and no errors? I certainly get errors, I need to go on a hunt for the 32bit version of that lib now.

[sangaya@FC5 SecondLife_i686_1_12_1_13]$ uname -a
Linux FC5 2.6.17-1.2187_FC5 #1 SMP Mon Sep 11 01:16:59 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
[sangaya@FC5 SecondLife_i686_1_12_1_13]$ ./secondlife
bin/secondlife-bin: error while loading shared libraries: libSDL-1.2.so.0: cannot open shared object file: No such file or directory

Merrick is on crack. BTW its not Red Hat any more its Fedora. Fedora installs both 32 and 64 bit versions of all libs by default. Thus unless you've specifically removed it, you probably have the 32bit SDL there if SDL is installed at all.

And no, 32bit programs can not use 64bit libraries, period. Nor can 64bit programs use 32bit libraries. I don't know where you're getting this "not fully 64bit" crap from. You can't mix the two, it HAS to be, and is, fully x86-64.

A 32bit program can make a 32bit call to a 64bit library, the 64bit library should respond 32bit. A 32bit program can not make a 64bit call. Thus, a 32bit program can run and reference 64bit libs in supported cases. In the case of libSDL and libuuid it can not be done, thus the 32bit libs must be used. Thus there are a few debian based distros that do not have 32bit libs, such as Ubuntu.

As for calling it Red Hat. The company is still Red Hat, their free linux OS is Fedora. I was speaking of everything Red Hat derived.

So! Here is the thing, x86_64 users can run their OS as 64bit, but may have a lot of 32bit programs on it, like X, FireFox etcetc, can even use 32bit drivers for some things. There is a question of stability. Such as SL is 32bit running on 64 bit hardware running an OS that has 32bit compatibility.

32bit programs CAN use 64bit libraries, it might not always end up with the desired result.

Actually, RHEL derives from Fedora. You've got it backwards.

Sidenotes:
http://en.wikipedia.org/wiki/Redhat
http://en.wikipedia.org/wiki/Fedora_Project

libSDL and libuuid interface in a two way relationship, my guess is suggesting that SL --(32bit data)--> SDL is okay but SDL --(64bit data)--> SL is not OK. Meaning that the 64 bit SDL library can receive either 32bit or 64bit data and understand it as on some linux systems the library has been converted to 64bit, but the library returns only 64bit data to SL which will confuse SL as it is not 64bit aware and truncating such mangles and causes the loss of important data. The same appears to go for libuuid. But allowing SL to communicate with 32bit SDL and uuid moves the 32/64bit crossovers to library and system communications that are able to handle that.

Error pushing 64bit libSDL: bin/secondlife-bin: error while loading shared libraries: libSDL-1.2.so.0: wrong ELF class: ELFCLASS64

Error pushing 64bit libuuid: bin/secondlife-bin: error while loading shared libraries: libuuid.so.1: wrong ELF class: ELFCLASS64

These libraries are for media access and unique identifier creation. Respectively http://www.libsdl.org/ and http://linux.about.com/library/cmd/blcmdl3_libuuid.htm for more info on these libraries.

This only causes a problem for users of 64bit systems who do not have 32 bit libuuid or libSDL libraries. For the distribution used find the 32bit library and place it in your secondlife/lib.

You're just sounding more and more crazy.