Re: gcc options

Hi Florin,

> > > However, xine-lib (latest version) decided to add "-mcpu=athlon",
> > > which is strange, because that's neither compatible with the
> > > -march i specified, nor is the exact match to the actual CPU in
> > > my system (which is an AthlonXP 1800).
> >
> > Did you pass your system type to configure?
> > Like "./configure --host=athlon-xp-suse-linux"
>
> No, but... why should that matter?
> Normally, a gcc parameter passed by the user via CFLAGS should
> override the defaults. At least, that's what most of the other
> applications do.

In general, user-specified CFLAGS are simply added to the ones the 
configure wants. It would be quite a bit of work to really parse them 
and I think no configure script anywhere does that.
The proper way is to help configure with the guesswork by using the host 
option. If you are doing an RPM build anyway, you could use the 
%configure macro which should do all that for you (if it's properly 
defined).

Michael

-- 
recursive
  see: recursive
        -RfC 1983



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01