On 02.13 Andrej Borsenkow wrote:
> > "Andrej Borsenkow" <[EMAIL PROTECTED]> writes:
> >
> > > Building kernel-2.4.1-mdk4 SRPM with
> > >
> > > rpm -ivh /path/to/kernel-2.4.1-4mdk.src.rpm
> > > cd /usr/src/RPM
> > > rpm -bb --target i586-mandrake-linux SPECS/kernel.spec
> > >
> > > I noticed that ALSA stuff still was compiled with -m486 flag. I
> > do not care
> > > much, but just for the sake of consistency ... and what if
> > anybody would like
> > > to build i386 system? :-)
> >
> > we don't do any optimisations CPU on kernel drivers.
> >
Kernel 2.4 compiles optimized with -O2 and -march=i{3456}86 depending on the
processor selection you do. At least standard kernel packages in www.kernel.org.
>
> I am not sure that I understand. I told it to build RPM for i586 and the whole
> kernel stuff is compiled for i586 except ALSA that is compiled for i486. My
> concern is, if I tell it to build RPM for i386, ALSA still will be built for
> i486. That does not sound like a right thing.
It is a problem with ALSA's config.in. I build my kernel and alsa drivers,
and the configure script in ALSA does not use the CFGLAGS env variable:
CC=gcc CFLAGS="-O2 -march=i686" ./configure ....
make
and you get
gcc -m486....
It is hardcoded in ALSA's configure.in, -m486 for anything >= i486. You
will not have the problem with 386, because that is handled as -m386.
--
J.A. Magallon $> cd pub
mailto:[EMAIL PROTECTED] $> more beer
Linux werewolf 2.4.1-ac10 #1 SMP Sun Feb 11 23:36:46 CET 2001 i686
