On Mon, 2004-06-28 at 13:26, Sid Boyce wrote:
Jan wrote:
Hi,
after finally getting my MSI K8T Neo VIA SATA controller to work somewhat by turning on udma2 support, I ran into some new problems e.g. when trying to install the w32codecs for xine and also get them to work with xine (either the suse x86_64 rpms or my custom built packages from cvs).
But let me not bore you with these detail but ask some general questions for my understanding:
1.) As I understand 32bit programs can not dynamically link to 64bit .so libs. In no case. Can you confirm that? [I.e. my xine must be 32bit if I want to use the 32bit w32codecs] How can 64bit and 32bit program then interact at all? Only via sockets or rpc?
Correct, e.g my 32-bit plugins do not work with mozilla 64-bit, I had to install firefox from www.mozilla.org in order to get them working. Programs such as slmodem contain a 32-bit proprietary module and it won't build many other 32-bit sources.
2.) Could my remaining problems with my Athlon64 K8T board be related to the bios not being well tested when running in 64bit mode (due to the lack of a 64bit windows)?
In some cases Suse 9.1 AMD64 contains also 32bit versions of frequently used libraries.
Some will build with "linux32 make".
3) How can I compile/rebuild these libs preferably from the suse sources to a 32bit package and get the installation location right (relocation). Using linux32 and rpmbuild or simply from 32bit suse 9.1 DVDs as binary rpms?
4) How do I relocate non-suse source rpms correctly so that when I compile to 64bit, they end up in the correct /usr/lib64 directories? And then when I start the app how does it know where to find the 64bit .so libs?
I haven't look very much at this, but it seems some sources need alteration. I tried building the sources to kmymoney and whatever I did, it kept looking in /usr/lib for one library that was in /usr/lib/lib64, for all the other libraries, it looked in 64 libs.
5) *-devel packages are noarch (i.e. they work for both 32 and 64 bit), correct?
The header files definitely are used by both. I haven't checked, but that's probably all they contain.
6) Is there is method to change compiler flags (e.g. add -fPIC) when building a package without actually unpacking, changing the spec file, repacking and trying it again?
??
Then finally just out of general interest, has anybody ever benchmarked the 32bit Suse Linux against its 64bit sister on the same Athlon64 machine?
Right this has been done! Running in 32bit mode with 32bit kernel , vs 64bit kernel and 64bit apps... same machine. Results are good Gimp2 is used as the example app benchmarks... Hold on i'll find the link:... http://translate.google.com/translate?u=http%3A%2F%2Fplanet64bit.de%2Fmodules%2Fnews%2Farticle.php%3Fstoryid%3D115&langpair=de%7Cen&hl=en&ie=UTF-8&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Note the original article is in german and here: http://planet64bit.de/modules/news/article.php?storyid=115
I saw benchmarks on the web some time ago, but they compared something like XP and 32-bit Linux. I think it would depend on the relative content of the 64-bit box as for sure the 64-bit apps would run way faster. A real test would be against an all 64-bit distro, probably a few years away. All I can say is that my Acer 1501LCe laptop with 9.1 x86_64 XP3000+ at 1.8 GHz is very fast compared to my XP2800+ at 2.097 GHz, I can start a kernel compile 5 minutes later on the laptop and it completes well before the XP2800+ 32-bit.
I searched on the web quite a bit but couldn't find any good explanations. Therefore Any hints or links would be greatly appreciated.
Nothing that compared a Linux mixed 64/32-bit distro and a plain 32-bit distro. Regards Sid.
-- Sid Boyce .... Hamradio G3VBV and keen Flyer ===== LINUX ONLY USED HERE =====