Compiling GLIBC on Linux. Oh golly gosh!
So, I could be wrong here, but did you try checking to see whether he is running a 32-bit install? Its obvious that you are running a 64-bit install...is it possible he has a 32?
Author
He has 64 bit. But that's another good point.. obviously I want my game to be playable on both 32 and 64 bit installations. What's the best way to deal with this? Is it possible to create 1 binary that will work on both? Or do I need to build 2 separate binaries?
Create an LSB-compliant 32-bit binary, make sure your program depends on the proper 32-bit packages. Unless you're going to use 2+ gigs of RAM, there's no point in also creating a 64-bit binary.
He has 64 bit. But that's another good point.. obviously I want my game to be playable on both 32 and 64 bit installations. What's the best way to deal with this? Is it possible to create 1 binary that will work on both? Or do I need to build 2 separate binaries?
Author
Hmm ok. So can I create 32 bit chroot environment and compile within that? Any suggestions? Or do I need to add some compiler flag to make it 32bit (I'm on a 64bit machine).
Create an LSB-compliant 32-bit binary, make sure your program depends on the proper 32-bit packages. Unless you're going to use 2+ gigs of RAM, there's no point in also creating a 64-bit binary.
[quote name='bencelot' timestamp='1296870928' post='4769848']
He has 64 bit. But that's another good point.. obviously I want my game to be playable on both 32 and 64 bit installations. What's the best way to deal with this? Is it possible to create 1 binary that will work on both? Or do I need to build 2 separate binaries?
[/quote]
Except all those additional juicy registers and a better ABI, and SSE2 minspec. No reason at all
Except all those additional juicy registers and a better ABI, and SSE2 minspec. No reason at all
More registers are fine, but the performance benefit is mitigated by the fact that the larger memory footprint of 64-bit code leads to more cache trashing. In effect, performance of 64-bit code can be worse than 32-bit code.
Create an LSB-compliant 32-bit binary, make sure your program depends on the proper 32-bit packages. Unless you're going to use 2+ gigs of RAM, there's no point in also creating a 64-bit binary.
[quote name='valderman' timestamp='1296905086' post='4769956']
[quote name='bencelot' timestamp='1296870928' post='4769848']
He has 64 bit. But that's another good point.. obviously I want my game to be playable on both 32 and 64 bit installations. What's the best way to deal with this? Is it possible to create 1 binary that will work on both? Or do I need to build 2 separate binaries?
[/quote]
Except all those additional juicy registers and a better ABI, and SSE2 minspec. No reason at all
[/quote]Then it's better to just compile a second binary with -msse2. As demonkoryu says, more registers and fancier instructions do nothing for you if you hit RAM all the time. Add in the porting issues you get for using a low-level language and maintaining two binaries suddenly seems a lot less attractive.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
