okay so i finally managed to coax configure and this is the result of 
running make:

make[3]: Entering directory `/home/mgc/src/mpeg4ip-0.9.1/lib/config_file'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/mgc/src/mpeg4ip-0.9.1/lib/config_file'
Making all in gnu
make[3]: Entering directory `/home/mgc/src/mpeg4ip-0.9.1/lib/gnu'
Making all in getopt
make[4]: Entering directory `/home/mgc/src/mpeg4ip-0.9.1/lib/gnu/getopt'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/home/mgc/src/mpeg4ip-0.9.1/lib/gnu/getopt'
make[4]: Entering directory `/home/mgc/src/mpeg4ip-0.9.1/lib/gnu'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/home/mgc/src/mpeg4ip-0.9.1/lib/gnu'
make[3]: Leaving directory `/home/mgc/src/mpeg4ip-0.9.1/lib/gnu'
Making all in mp4
make[3]: Entering directory `/home/mgc/src/mpeg4ip-0.9.1/lib/mp4'
/bin/sh ../../libtool --mode=compile arm-linux-gcc -DHAVE_CONFIG_H -I. 
-I. -I../
.. -I../../include    -g -O2 -c rtphint.c
../../libtool: test: =: unary operator expected
rm -f .libs/rtphint.lo
arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -g -O2 
-Wp,-MD,.de
ps/rtphint.pp -c rtphint.c  -fPIC -DPIC -o .libs/rtphint.lo
/tmp/ccF7TKZc.s: Assembler messages:
/tmp/ccF7TKZc.s:526: Error: bad instruction `rorw $8,r0'
/tmp/ccF7TKZc.s:675: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:677: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:687: Error: bad instruction `rorw $8,r4'
/tmp/ccF7TKZc.s:693: Error: bad instruction `rorw $8,r5'
/tmp/ccF7TKZc.s:785: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:818: Error: bad instruction `rorw $8,r4'
/tmp/ccF7TKZc.s:818: Error: bad instruction `rorl $16,r4'
/tmp/ccF7TKZc.s:818: Error: bad instruction `rorw $8,r4'
/tmp/ccF7TKZc.s:918: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:920: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:1013: Error: bad instruction `rorw $8,r5'
/tmp/ccF7TKZc.s:1019: Error: bad instruction `rorw $8,r6'
/tmp/ccF7TKZc.s:1019: Error: bad instruction `rorl $16,r6'
/tmp/ccF7TKZc.s:1019: Error: bad instruction `rorw $8,r6'
/tmp/ccF7TKZc.s:1023: Error: bad instruction `rorw $8,r7'
/tmp/ccF7TKZc.s:1023: Error: bad instruction `rorl $16,r7'
/tmp/ccF7TKZc.s:1023: Error: bad instruction `rorw $8,r7'
/tmp/ccF7TKZc.s:1037: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:1039: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:1286: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1304: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1310: Error: bad instruction `rorw $8,r7'
/tmp/ccF7TKZc.s:1452: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1452: Error: bad instruction `rorl $16,r2'
/tmp/ccF7TKZc.s:1452: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1478: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1490: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1507: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1531: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:1531: Error: bad instruction `rorl $16,r3'
/tmp/ccF7TKZc.s:1531: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:1632: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:1733: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1733: Error: bad instruction `rorl $16,r2'
/tmp/ccF7TKZc.s:1733: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1742: Error: bad instruction `rorw $8,r0'
/tmp/ccF7TKZc.s:1742: Error: bad instruction `rorl $16,r0'
/tmp/ccF7TKZc.s:1742: Error: bad instruction `rorw $8,r0'
/tmp/ccF7TKZc.s:1938: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1950: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1950: Error: bad instruction `rorl $16,r2'
/tmp/ccF7TKZc.s:1950: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1962: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1962: Error: bad instruction `rorl $16,r2'
/tmp/ccF7TKZc.s:1962: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1974: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:1991: Error: bad instruction `rorw $8,r2'
/tmp/ccF7TKZc.s:2058: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2132: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2132: Error: bad instruction `rorl $16,r3'
/tmp/ccF7TKZc.s:2132: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2180: Error: bad instruction `rorw $8,r4'
/tmp/ccF7TKZc.s:2231: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2272: Error: bad instruction `rorw $8,r8'
/tmp/ccF7TKZc.s:2282: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2282: Error: bad instruction `rorl $16,r3'
/tmp/ccF7TKZc.s:2282: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2291: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2291: Error: bad instruction `rorl $16,r3'
/tmp/ccF7TKZc.s:2291: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2300: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2300: Error: bad instruction `rorl $16,r3'
/tmp/ccF7TKZc.s:2300: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2309: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2309: Error: bad instruction `rorl $16,r3'
/tmp/ccF7TKZc.s:2309: Error: bad instruction `rorw $8,r3'
/tmp/ccF7TKZc.s:2358: Error: bad instruction `rorw $8,r0'
/tmp/ccF7TKZc.s:2400: Error: bad instruction `rorw $8,r3'
make[3]: *** [rtphint.lo] Error 1
make[3]: Leaving directory `/home/mgc/src/mpeg4ip-0.9.1/lib/mp4'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/mgc/src/mpeg4ip-0.9.1/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/mgc/src/mpeg4ip-0.9.1'
make: *** [all-recursive-am] Error 2



does anybody know what is happening? thanx in advance,




[EMAIL PROTECTED] wrote:

> On Wed 21 Nov, TheMaverickMind wrote:
> 
>>We desprately need help:
>>
>>We are working on an application to distribute MP4 video on the Compaq  
>>iPAQ. We want to install the mp4player [available on 
>>mpeg4ip.sourceforge.net] on the iPAQ which is running arm-linux. We 
>>decided to cross-compile the application from our Debian Potato hosts 
>>[kernel version 2.2.17 and kernel version 2.2.19Pre17 both available].
>>
>>We have set up the toolchain available from Debian including the glibc, 
>>gcc, and binutils. 
>>
> 
> Which toolchain exactly? personally I favour the emdebian (x86->arm)
> toolchain (http://www.emdebian.org/ ) which is apt-gettable and reliable. See
> http://www.aleph1.co.uk/armlinux/book/x1768.html for details of this. I
> assume your host is an x86 machine?
> 
> 
>>we have also downloaded the kernel headers and  libraries. but we are
>>unable to compile mp4player for arm-linux. 
>>
> 
> You understand that you need the kernel headers and libraries that match the
> _arm_ environment you are compiling for, not the host machine? ie you need
> 2.4.whatever kernel headers, not the 2.2.x that matches your (x86?) potato
> box.
> 
> The debian tool dpkg-cross is useful for stripping the libraries and headers
> out of a binary-arm package to make a package with just those in which can be
> installed and deinstalled in the usual way. This lets you control the
> available headers and libs using the package-management system, which is
> handy if you do much of it.
> 
> 
>>What  options are to be used while running the configure and make commands?
>>
> 
> ./configure arm-linux is usually sufficient, if configure complains of unkown
> targets try:   ./configure arm-unknown-linux-gnu
> 
> The detailed options to get it to do what you want are:
> --build specifies the machine you want to build on
> --host specifies the machine you want the compiled program to run on
> --target (only for compilers and the like) controls the machine that the
> newly-built compiler will compile for for.
> 
> The autoconf docs explain this in more detail in the 'Manual configuration'
> section.
>  
> 
>>in general, for applications that use autoconf and automake to configure 
>>the makefiles, how do we cross compile to arm-linux?
>>
> 
> Well, first you try the above options, but in many cases (where the configure
> stuff was not written with cross-compiling in mind), you will need to modify
> the makefiles to get it to do the right thing, eg to specify the directory
> where it will find your arm header files and libraries.
>  
> 
>>Help is reqd urgently can anyone please guide us?  Is any further 
>>information required?
>>
> 
> Well, I was going to download this and try it myself to see what went wrong
> but it's 7MB and hasn't finished yet, so see if the above helps...
> 
> Wookey
> 



_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.

Reply via email to