AW: [suse-amd64] Xine and 64bit windows codecs
Just an idea: put a linux32 in front of the configure call. linux32 switches the system identify to a 32-bit 686 system for the commands. linux32 ./configure This in addition to set the CFLAGS and LDFLAGS to the -m32 architecture. Doing this helped in some of my config problems. Another idea is to recreate the configure file if the files configure.ac (or configure.in) Makefile.am (these also in the subdirectories) are available. Then you are able to run linux32 ./autogen.sh this shell script calls a number of programms to recereate the configure, makefile, etc. Regards, Werner
-----Ursprüngliche Nachricht----- Von: Tim Janssen [mailto:timtjanssen@yahoo.com] Gesendet: Samstag, 4. März 2006 19:01 An: Manuel Soriano; suse-amd64@suse.com Betreff: Re: [suse-amd64] Xine and 64bit windows codecs
Thanks you all, for the abundant info on this. I am fine with sticking to 32 bit for now. However, how do I compile Mplayer in 32bit mode? Manu suggested
And change, in the configure, the search order of the libraries :
/usr/lib:/usr/lib64 instead of /usr/lib64:/usr/lib
but I have been unable to find these lines in the CVS version configure file. When I ignore that bit and simply set the flags (as Manu also suggested)
export CFLAGS=-m32 export LDFLAGS=-m32
doing a configure/make results in a mess:
wrapper.S: Assembler messages: wrapper.S:25: Error: `pusha' is not supported in 64-bit mode wrapper.S:28: Error: suffix or operands invalid for `push' wrapper.S:32: Error: suffix or operands invalid for `push' wrapper.S:34: Error: suffix or operands invalid for `push' wrapper.S:39: Error: suffix or operands invalid for `push' wrapper.S:40: Error: suffix or operands invalid for `push' wrapper.S:49: Error: `popa' is not supported in 64-bit mode wrapper.S:51: Error: suffix or operands invalid for `pop' wrapper.S:52: Error: suffix or operands invalid for `push' wrapper.S:58: Error: suffix or operands invalid for `push' wrapper.S:59: Error: `pusha' is not supported in 64-bit mode wrapper.S:62: Error: suffix or operands invalid for `push' wrapper.S:66: Error: suffix or operands invalid for `push' wrapper.S:68: Error: suffix or operands invalid for `push' wrapper.S:73: Error: suffix or operands invalid for `push' wrapper.S:74: Error: suffix or operands invalid for `push' wrapper.S:81: Error: `popa' is not supported in 64-bit mode make[1]: *** [wrapper.o] Error 1
Thus: how to compile mplayer as a 32bit application?
Thanks! Tim
--- Manuel Soriano
wrote: El Sábado 04 Marzo 2006 13:50, Tom Corr escribió:
On Friday 03 March 2006 09:04, Manuel Soriano wrote:
For a while i don't use other viewer than mplayer :
http://www.mplayerhq.hu/design7/dload.html
very easy to configure, compile & using...
mplayer have some problems in 64bit & with the compiler included in the Suse-10.0, you have some solutions :
compile in 32bit mode with the stock compiler compile in 32bit mode with the old gcc compiler compile in 64bit mode with the stock compiler,but with some restrictions, like the windows codes cimpile in 64bit mode with the old gcc compiler, with the same restrictions.
The old gcc compiler gives you more stability when you copy "autorised" pictures... I use the version 3.3.6 of the gcc.
To compile in 32bit mode, you need to declare two variables :
export CFLAGS=-m32 export LDFLAGS=-m32
And change, in the configure, the search order of the libraries :
/usr/lib:/usr/lib64 instead of /usr/lib64:/usr/lib
Enjoy...
--
Bye, Manu.
Break the rules! Break the windows! Use Linux! manu at valux.org http://www.valux.org Linux is here to stay. FUD won't make it go away. ************************************************* * Manuel Soriano * Lo Perello/Valencia/Spain * ( AbM Compliant ) Linux Counter Nº: 294597 Para que funcione la alianza de civilizaciones, todos deben ser civilizados.
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
On Tue, Mar 07, 2006 at 08:59:36AM +0100, Dittmann, Werner wrote:
Just an idea: put a linux32 in front of the configure call. linux32 switches the system identify to a 32-bit 686 system for the commands.
linux32 ./configure
This in addition to set the CFLAGS and LDFLAGS to the -m32 architecture.
I found sometimes that it was just easier to set CC to 'gcc -m32' as there were sometimes calls to CC without the flags. And if there are any direct calls to ld, either add a -32 flag, or replace the ld calls with 'gcc -m32' and it'll call ld with the right flags. My steps to building 32bit package are usually: linux32 /bin/bash # Easier to just use a shell vim <spec> # Add 32bit to pkg name so you get a <pkg>-32bit-<ver> rpm CC='gcc -m32' rpmbuild -bb <spec> -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com My BBS is baroque now. Please call Bach later with your Handel.
Mike Marion wrote:
On Tue, Mar 07, 2006 at 08:59:36AM +0100, Dittmann, Werner wrote:
Just an idea: put a linux32 in front of the configure call. linux32 switches the system identify to a 32-bit 686 system for the commands.
linux32 ./configure
This in addition to set the CFLAGS and LDFLAGS to the -m32 architecture.
I found sometimes that it was just easier to set CC to 'gcc -m32' as there were sometimes calls to CC without the flags.
And if there are any direct calls to ld, either add a -32 flag, or replace the ld calls with 'gcc -m32' and it'll call ld with the right flags.
My steps to building 32bit package are usually: linux32 /bin/bash # Easier to just use a shell vim <spec> # Add 32bit to pkg name so you get a <pkg>-32bit-<ver> rpm CC='gcc -m32' rpmbuild -bb <spec>
--Thanks everybody for this lively discussion about 32-bit installs. I have two questions regarding 32-bit programs under a 64-bit kernel: (1) In my '/usr/src/packages/RMPS/x86_64' directory I see a file named 'w32codec-all-20050412-0.pm.0.x86_64.rpm', whose name suggests it is a a 64-bit file handling windows codecs. I downloaded it (I think in src.rpm format) some time ago. Are this 64-bit Linux codecs which can handle the 32-bit Windows codecs, so, say a 64-bit Xine can play, say, wmv files? (2) I tried to install transcode from the apt-get 64-bit repositories via synaptic. Synaptic, among other things, complains that MPlayer, which is 32-bits, needs to be uninstalled (I installed the 32-bit rpm version from Packman). Why so if MPlayer is 32 bits and transcode is 64 bits? Can't rpm tell the difference between 64-bit and 32-bit packages? The dependency libraries for 32-bit software are installed in '/lib', while the ones for 64-bit programs in '/lib/64'. Is it possible to have a 32-bit MPlayer and a 64-bit transcode and also 64-bit kino installed? CF -- Running 64-bit Linux on AMD64
Constantine 'Gus' Fantanas wrote:
Mike Marion wrote:
On Tue, Mar 07, 2006 at 08:59:36AM +0100, Dittmann, Werner wrote:
Just an idea: put a linux32 in front of the configure call. linux32 switches the system identify to a 32-bit 686 system for the commands.
linux32 ./configure
This in addition to set the CFLAGS and LDFLAGS to the -m32 architecture.
I found sometimes that it was just easier to set CC to 'gcc -m32' as there were sometimes calls to CC without the flags.
And if there are any direct calls to ld, either add a -32 flag, or replace the ld calls with 'gcc -m32' and it'll call ld with the right flags.
My steps to building 32bit package are usually: linux32 /bin/bash # Easier to just use a shell vim <spec> # Add 32bit to pkg name so you get a <pkg>-32bit-<ver> rpm CC='gcc -m32' rpmbuild -bb <spec>
--Thanks everybody for this lively discussion about 32-bit installs. I have two questions regarding 32-bit programs under a 64-bit kernel:
(1) In my '/usr/src/packages/RMPS/x86_64' directory I see a file named 'w32codec-all-20050412-0.pm.0.x86_64.rpm', whose name suggests it is a a 64-bit file handling windows codecs. I downloaded it (I think in src.rpm format) some time ago. Are this 64-bit Linux codecs which can handle the 32-bit Windows codecs, so, say a 64-bit Xine can play, say, wmv files?
(2) I tried to install transcode from the apt-get 64-bit repositories via synaptic. Synaptic, among other things, complains that MPlayer, which is 32-bits, needs to be uninstalled (I installed the 32-bit rpm version from Packman). Why so if MPlayer is 32 bits and transcode is 64 bits? Can't rpm tell the difference between 64-bit and 32-bit packages? The dependency libraries for 32-bit software are installed in '/lib', while the ones for 64-bit programs in '/lib/64'. Is it possible to have a 32-bit MPlayer and a 64-bit transcode and also 64-bit kino installed?
CF
-- Running 64-bit Linux on AMD64
Hi, for your first question: I installed this package and can now play wmv-files in Mplayer and Xine, both 64bit. for the second: I have installed all those apps in 64bit, I think you had to install the 32bit version of transcode to get it running. Michael
participants (4)
-
Constantine 'Gus' Fantanas
-
Dittmann, Werner
-
Michael Steinhauser
-
Mike Marion