Linux users: which Distribution are you running?
Moderator: Oberlus
Linux users: which Distribution are you running?
I would like to get an overview of the distributions we should provide packages for, so please tell me what distribution you are using. If I forgot any, please post the name of your distribution.
Please post the version of your distribution, too. I do not want to make a list consisting of "SuSE 8.0" "SuSE 8.1", "SuSE 9.0" etc.
Oh, and if you are willing to create a package for your distro (I can only provide .debs for Debian), please let me know.
Please post the version of your distribution, too. I do not want to make a list consisting of "SuSE 8.0" "SuSE 8.1", "SuSE 9.0" etc.
Oh, and if you are willing to create a package for your distro (I can only provide .debs for Debian), please let me know.
I'm running Debian Testing but i think they just recently officially upgraded, didn't they? I've stopped regularly updating the entire system because updates sometimes save over customized config files and can trash my rocksolid setup. So unless i need new software, i don't really upgrade anymore. I'd rather just work with what i've got that i know for sure works.
Well, that's what stable is for. Only security updates, and guaranteed to leave your setup alone and not change any behaviour at all.leiavoia wrote:I've stopped regularly updating the entire system because updates sometimes save over customized config files and can trash my rocksolid setup.
BTW: Debian Sarge was released in July, IIRC.
[noobspeak]Yoghurt wrote:Of course it would. Only that the binary does not work and probably never will due to incompatible C++ ABIsquork wrote: I think that providing autopackage resolves RPM based distros
This is one of the few things Windows can do better than Linux.
Are there any compatibility layer libraries?
[/noobspeak]
Nope, because it's impossible. ABI, not APImuxec wrote:Are there any compatibility layer libraries?
See here what wikipedia has to say about ABIs.
I thought autopackage has automatic resolving of ld dependencies. But you have to substitute dlopen() with autopackage provided function in the FO code.Yoghurt wrote:Of course it would. Only that the binary does not work and probably never will due to incompatible C++ ABIsquork wrote: I think that providing autopackage resolves RPM based distros
This is one of the few things Windows can do better than Linux.
The emperor wants to control outer space. Yoda wants to control inner space. That's the fundamental difference between the good and the bad sides of the force... - Mof, Human Traffic
Unfortunately, it has nothing to do with this.
The problem is the following:
Suppose (theoretically) strings were stored in the 1.02 ABI as "length, bytes, bytes, ..." (for example : "9FreeOrion"), the ABI version 2 of g++ now stores them as word, word, word,... ("F_r_e_O_r_i_o_n_") - now imagine a function compiled with Version 2 calls a function in a library compiled with version 1 that takes a string as argument. the function expects "9Freeorion" but gets the other -> crash.
There might be a way to work around all that, but that is stuff for 0.31, at the moment, I'm preparing deb packages, as 0.3 must be out soon. If the debs are finished, I might take another look at the autopackage.
The problem is the following:
Suppose (theoretically) strings were stored in the 1.02 ABI as "length, bytes, bytes, ..." (for example : "9FreeOrion"), the ABI version 2 of g++ now stores them as word, word, word,... ("F_r_e_O_r_i_o_n_") - now imagine a function compiled with Version 2 calls a function in a library compiled with version 1 that takes a string as argument. the function expects "9Freeorion" but gets the other -> crash.
There might be a way to work around all that, but that is stuff for 0.31, at the moment, I'm preparing deb packages, as 0.3 must be out soon. If the debs are finished, I might take another look at the autopackage.
You might want to check this out:
http://www.bitrock.com/products_install ... rview.html
It's free for opensource projects.
http://www.bitrock.com/products_install ... rview.html
It's free for opensource projects.
How happens that binaries from Loki work on all platforms?Yoghurt wrote:Nope, because it's impossible. ABI, not APImuxec wrote:Are there any compatibility layer libraries?
See here what wikipedia has to say about ABIs.
Ok. Now I understand. However I still think that I have seen somewhere in the documentation that autopackage takes care of such things. AFAIK autopackage was made to be the system independent 3rd-party package manager and they've takes care of most problems that could arise from this independancy.Yoghurt wrote:Unfortunately, it has nothing to do with this.
The problem is the following:
Suppose (theoretically) strings were stored in the 1.02 ABI as "length, bytes, bytes, ..." (for example : "9FreeOrion"), the ABI version 2 of g++ now stores them as word, word, word,... ("F_r_e_O_r_i_o_n_") - now imagine a function compiled with Version 2 calls a function in a library compiled with version 1 that takes a string as argument. the function expects "9Freeorion" but gets the other -> crash.
There might be a way to work around all that, but that is stuff for 0.31, at the moment, I'm preparing deb packages, as 0.3 must be out soon. If the debs are finished, I might take another look at the autopackage.
If it's not your priority, no problem. I have CVS code regularly updated. However the latest CVS is broken as hell.
The emperor wants to control outer space. Yoda wants to control inner space. That's the fundamental difference between the good and the bad sides of the force... - Mof, Human Traffic
Yes, but they also mention it doesn't really work for C++ projects.Wolverine wrote:Ok. Now I understand. However I still think that I have seen somewhere in the documentation that autopackage takes care of such things.
Then please, please, submit bug reports ASAP, as the CVS currently is identical with the upcoming 0.3 releaseHowever the latest CVS is broken as hell.