On Fri, Dec 26, 2008 at 4:07 PM, Axel Thimm <[email protected]> wrote:

> Hi,
>
> On Fri, Dec 26, 2008 at 02:35:54PM -0200, Paulo Cavalcanti wrote:
> > On Fri, Dec 26, 2008 at 11:35 AM, Paulo Cavalcanti <[email protected]>
> wrote:
> > > On Fri, Dec 26, 2008 at 11:29 AM, Stefan Smietanowski <
> [email protected]>wrote:
> > >> Paulo Cavalcanti wrote:
> > >>
> > >>> Axel,
> > >>>
> > >>> I think you will not be able to compile alsa-driver for the new F10
> > >>> kernel.
> > >>>
> > >>> Fedora defined fmode_t in the kernel, and it is conflicting with
> > >>> the definition in the alsa tarball.
>
> Yes, thanks, I saw that is morning. :(
>
> > >>> I do not see an elegant way to patch it, because the test in the
> tarball
> > >>> if for kernels < 2.6.28.  Furthermore, it was not supposed to appear
> > >>> a new typedef in the 2.6.27 kernel.
>
> Perhaps it's one of the backported patches from 2.6.28. There are at
> least two, but I didn't look deeper into this - part of the next
> kernels are quite often appearing in Fedora and more often in RHEL
> kernels requiring quirks and patches.
>
> > Here is the error. Some new symbols have just "appeared" in the kernel
> ...
> >
> > this is the location of the previous definition
> > In file included from include/linux/sched.h:86,
> >                  from include/linux/smp_lock.h:5,
> >                  from include/linux/hardirq.h:5,
> >                  from include/linux/interrupt.h:11,
> >                  from
> >
> /builddir/build/BUILD/alsa-driver/drivers/pcsp/../../alsa-kernel/drivers/pcsp/pcsp_lib.c:11,
> >                  from
> > /builddir/build/BUILD/alsa-driver/drivers/pcsp/pcsp_lib.c:5:
> > include/linux/hrtimer.h:249: error: expected identifier or '(' before
> > 'const'
>
> Are these new symbols comflicting with ones from alsa, too?
>

Yes. Removing the definition of fmode_t in the tarball, this is the only
error I got.

I am so close to fix the sigmatel codec for my cards , and now  this kernel
with some
new symbols.


-- 
Paulo Roma Cavalcanti
LCG - UFRJ
_______________________________________________
atrpms-devel mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/atrpms-devel

Reply via email to