madplayer cross-compile on ARM11 compilation error "impossible constraint in 'asm'"

[Jianfeng Li]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi, All,
 
I am now trying to cross-compile the madplayer on an arm11 based embedded system.  The compiler I am using is from montavista mobilinux 5.0.
 
When I tried to build the madplay, for the file resample.c, I got 2 errors on line 89 and 104.  The error information is "impossible constraint in 'asm'.  When I tried to build the libmad, I also met the same error.  But it seems that during compilation if "FPM-ARM" option is enabled then the error is solved.  But here I checked the Makefile, there is no such option of "FPM" as in the Makefile of libmad. 
 
So can anybody help to tell me why this error happens, it is due to the compiler's constraint/requirement?  How should I try to solve this error?  Is "trying to enable the FPM" a good option to try?
 
Many thanks in advance!
 
Regards,
Jeffen
 

---

Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it!

[Rob Leslie]

On May 18, 2008, at 12:33 AM, Jianfeng Li wrote:

> I am now trying to cross-compile the madplayer on an arm11 based  
> embedded system.  The compiler I am using is from montavista  
> mobilinux 5.0.
>
> When I tried to build the madplay, for the file resample.c, I got 2  
> errors on line 89 and 104.  The error information is "impossible  
> constraint in 'asm'.  When I tried to build the libmad, I also met  
> the same error.  But it seems that during compilation if "FPM-ARM"  
> option is enabled then the error is solved.  But here I checked the  
> Makefile, there is no such option of "FPM" as in the Makefile of  
> libmad.
>
> So can anybody help to tell me why this error happens, it is due to  
> the compiler's constraint/requirement?  How should I try to solve  
> this error?  Is "trying to enable the FPM" a good option to try?

Running the libmad `configure' script is the usual way to cause an  
appropriate FPM macro to be defined. You can force the selection using  
the --enable-fpm option (e.g. --enable-fpm=arm) in case the  
automatically chosen default is inappropriate for some reason.

Note that the FPM selection is carried into the mad.h header file  
which is used by madplay et al. When cross-compiling, the resulting  
mad.h could be different from the build system's mad.h so it's  
important to check your include paths.

--
Rob Leslie
rob@...

[Jianfeng Li]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Thank you so much for your help, Rob!
 
Regards,
Jeff

---

> From: rob@...

> To: mad-dev@...
> Date: Sun, 18 May 2008 19:40:12 -0700
> Subject: Re: [mad-dev] madplayer cross-compile on ARM11 compilation error "impossible constraint in 'asm'"
>
> On May 18, 2008, at 12:33 AM, Jianfeng Li wrote:
> > I am now trying to cross-compile the madplayer on an arm11 based
> > embedded system. The compiler I am using is from montavista
> > mobilinux 5.0.
> >
> > When I tried to build the madplay, for the file resample.c, I got 2
> > errors on line 89 and 104. The error information is "impossible
> > constraint in 'asm'. When I tried to build the libmad, I also met
> > the same error. But it seems that during compilation if "FPM-ARM"
> > option is enabled then the error is solved. But here I checked the
> > Makefile, there is no such option of "FPM" as in the Makefile of
> > libmad.
> ! >
> > So can anybody help to tell me why this error happens, it is due to
> > the compiler's constraint/requirement? How should I try to solve
> > this error? Is "trying to enable the FPM" a good option to try?
>
> Running the libmad `configure' script is the usual way to cause an
> appropriate FPM macro to be defined. You can force the selection using
> the --enable-fpm option (e.g. --enable-fpm=arm) in case the
> automatically chosen default is inappropriate for some reason.
>
> Note that the FPM selection is carried into the mad.h header file
> which is used by madplay et al. When cross-compiling, the resulting
> mad.h could be different from the build system's mad.h so it's
> important to check your include paths.
>
> --
> Rob Leslie
> rob@...
>

---

Invite your mail contacts to join your friends list with Windows Live S! paces. It's easy! Try it!