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? 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. 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? 5) *-devel packages are noarch (i.e. they work for both 32 and 64 bit), correct? 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? I searched on the web quite a bit but couldn't find any good explanations. Therefore Any hints or links would be greatly appreciated. best regards, Jan
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?
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 =====
Hi all, Reply below. Best regards On Monday 28 June 2004 11:26, Sid Boyce wrote:
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.
Look at the configure script for the package and try to see if the following will work: ./configure --enable-libsuffix=64 This is a frequently asked question. See eg. http://lists.suse.com/archive/suse-amd64/2004-Jun/0272.html http://lists.suse.com/archive/suse-amd64/2004-May/0294.html http://lists.suse.com/archive/suse-amd64/2004-Apr/0217.html http://archives.mandrakelinux.com/cooker-amd64/2004-04/msg00033.php
Paul C. Leopardi wrote:
Hi all, Reply below. Best regards
On Monday 28 June 2004 11:26, Sid Boyce wrote:
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.
Look at the configure script for the package and try to see if the following will work:
./configure --enable-libsuffix=64
This is a frequently asked question. See eg. http://lists.suse.com/archive/suse-amd64/2004-Jun/0272.html http://lists.suse.com/archive/suse-amd64/2004-May/0294.html http://lists.suse.com/archive/suse-amd64/2004-Apr/0217.html http://archives.mandrakelinux.com/cooker-amd64/2004-04/msg00033.php
Been there, done that, but it doesn't work for all sources, e.g kmymoney-2.0.6rc4. libpcreposix.la is actually in /usr/lib64. I chose kmymoney as a random app to try as someone else had hit the same kind of problem with a quite different app. If I copy that lib into /usr/lib, it complains about /usr/lib/libpcre.la which again is in /usr/lib64, also libpcreposix.la has a line "dependancy_libs=' /usr/lib64/libpcre.la'. kmymoney builds its own libtool and perhaps that's where the problem is, but I haven't found anything that I can put a finger on and some changes made to libtool made no difference. ./configure --enable-libsuffix=64 --with-qt-dir=/usr/lib64/qt3 --prefix=/opt/kde3 --with-qt-libraries=/usr/lib64/qt3/lib64 --with-extra-libs=/usr/lib64 Then during make ============== /bin/sh ../libtool --mode=link --tag=CXX g++ -O2 -fno-exceptions -fno-check-new -fexceptions -lxml2 -lz -lpthread -lm -o kmymoney2 -L/usr/X11R6/lib64 -L/ usr/lib64/qt3/lib64 -L/opt/kde3/lib kmymoneyutils.o kstartuplogo.o kmymoney2.o main.o kmymoney2.moc.o kstartuplogo.moc.o kmymoney2_meta_unload.o ./views/ libviews.a ./converter/libconverter.a ./dialogs/libdialogs.a ./widgets/libwidgets.a ./mymoney/storage/libstorage.a ./mymoney/libmymoney.a -lkhtml -lkdeui - lkdecore -lqt-mt -lpng -lz -lm -lXext -lX11 -lresolv -lSM -lICE -lpthread -lresolv mkdir .libs libtool: link: cannot find the library `/usr/lib/libpcreposix.la' make[3]: *** [kmymoney2] Error 1 make[3]: Leaving directory `/ftp/apr04/kmymoney2-0.6rc4/kmymoney2' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/ftp/apr04/kmymoney2-0.6rc4/kmymoney2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/ftp/apr04/kmymoney2-0.6rc4' make: *** [all] Error 2 -------------------------------------------- With /usr/lib/libpcreposix.la copied over from /usr/lib64 libtool: link: cannot find the library `/usr/lib/libpcre.la' Hit the right app and you will have problems. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer ===== LINUX ONLY USED HERE =====
Hi Sid, On Tue, 29 Jun 2004, Sid Boyce wrote:
Been there, done that, but it doesn't work for all sources, e.g kmymoney-2.0.6rc4. libpcreposix.la is actually in /usr/lib64. I chose kmymoney as a random app to try as someone else had hit the same kind of problem with a quite different app. If I copy that lib into /usr/lib, it complains about /usr/lib/libpcre.la which again is in /usr/lib64, also libpcreposix.la has a line "dependancy_libs=' /usr/lib64/libpcre.la'. kmymoney builds its own libtool and perhaps that's where the problem is, but I haven't found anything that I can put a finger on and some changes made to libtool made no difference.
/bin/sh ../libtool --mode=link --tag=CXX g++ -O2 -fno-exceptions -fno-check-new -fexceptions -lxml2 -lz -lpthread -lm -o kmymoney2 -L/usr/X11R6/lib64 -L/ usr/lib64/qt3/lib64 -L/opt/kde3/lib kmymoneyutils.o kstartuplogo.o kmymoney2.o main.o kmymoney2.moc.o kstartuplogo.moc.o kmymoney2_meta_unload.o ./views/libviews.a ./converter/libconverter.a ./dialogs/libdialogs.a ./widgets/libwidgets.a ./mymoney/storage/libstorage.a ./mymoney/libmymoney.a -lkhtml -lkdeui - lkdecore -lqt-mt -lpng -lz -lm -lXext -lX11 -lresolv -lSM -lICE -lpthread -lresolv mkdir .libs libtool: link: cannot find the library `/usr/lib/libpcreposix.la'
Now copy-paste the above command but call the shell with -x, i.e. # /bin/sh -x ../libtool <all args from above> Redirect the output into a file. Look at that file. At which point does "/usr/lib/libpcreposix.la" into play? That should help in finding out which .la either references it, or at which point "/usr/lib" magically is added to the search path. Ciao, Michael.
Michael Matz wrote:
Hi Sid,
On Tue, 29 Jun 2004, Sid Boyce wrote:
Been there, done that, but it doesn't work for all sources, e.g kmymoney-2.0.6rc4. libpcreposix.la is actually in /usr/lib64. I chose kmymoney as a random app to try as someone else had hit the same kind of problem with a quite different app. If I copy that lib into /usr/lib, it complains about /usr/lib/libpcre.la which again is in /usr/lib64, also libpcreposix.la has a line "dependancy_libs=' /usr/lib64/libpcre.la'. kmymoney builds its own libtool and perhaps that's where the problem is, but I haven't found anything that I can put a finger on and some changes made to libtool made no difference.
/bin/sh ../libtool --mode=link --tag=CXX g++ -O2 -fno-exceptions -fno-check-new -fexceptions -lxml2 -lz -lpthread -lm -o kmymoney2 -L/usr/X11R6/lib64 -L/ usr/lib64/qt3/lib64 -L/opt/kde3/lib kmymoneyutils.o kstartuplogo.o kmymoney2.o main.o kmymoney2.moc.o kstartuplogo.moc.o kmymoney2_meta_unload.o ./views/libviews.a ./converter/libconverter.a ./dialogs/libdialogs.a ./widgets/libwidgets.a ./mymoney/storage/libstorage.a ./mymoney/libmymoney.a -lkhtml -lkdeui - lkdecore -lqt-mt -lpng -lz -lm -lXext -lX11 -lresolv -lSM -lICE -lpthread -lresolv mkdir .libs libtool: link: cannot find the library `/usr/lib/libpcreposix.la'
Now copy-paste the above command but call the shell with -x, i.e. # /bin/sh -x ../libtool <all args from above>
Redirect the output into a file. Look at that file. At which point does "/usr/lib/libpcreposix.la" into play? That should help in finding out which .la either references it, or at which point "/usr/lib" magically is added to the search path.
Ciao, Michael.
Same result. It still searches /usr/lib, even after I've altered every instance of lib to lib64 in libtool. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer ===== LINUX ONLY USED HERE =====
Hi, I upgraded the OS of my Opteron cluster from SLSE8 to SuSE 9.1, and installed the latest queueing system Torque-1.1.0p0 from Supercluster. However, I am not able to configure the server with qmgr, qmgr always returns a message "... Unauthorized Reqhests" for any command I type. I have no idea how to fix this problem and any suggestion/hint is appreciated. On SLSE8 for AMD64, Torque-1.0.1p6 was working normally, I saved the server configuration with command qmgr -c "print server" > server.conf and used the server.conf to configure Torque-1.1.0p0 on SuSE 9.1, but I got a "Unauthorized Requests" message for each line in file server.conf. Best regards Jyh-Shyong Ho, Ph.D. Research Scientist National Center for High Performance Computing Hsinchu, Taiwan, ROC "Paul C. Leopardi" wrote:
Hi all, Reply below. Best regards
On Monday 28 June 2004 11:26, Sid Boyce wrote:
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.
Look at the configure script for the package and try to see if the following will work:
./configure --enable-libsuffix=64
This is a frequently asked question. See eg. http://lists.suse.com/archive/suse-amd64/2004-Jun/0272.html http://lists.suse.com/archive/suse-amd64/2004-May/0294.html http://lists.suse.com/archive/suse-amd64/2004-Apr/0217.html http://archives.mandrakelinux.com/cooker-amd64/2004-04/msg00033.php
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
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 =====
participants (6)
-
Jan -
Joel Wiramu Pauling -
Jyh-Shyong Ho -
Michael Matz -
Paul C. Leopardi -
Sid Boyce