> there were bugs on rc1 for 2.2 kernels.  i fixed them recently on cvs.
> please try the cvs version.

Thanks for the quick reply.
I tried last night's cvs (2002-05-24.tar.bz2) and hit a few more snags ...

Problem 1:
==========
In alsa-driver, I couldn't persuade the snd-seq-oss.o module to build,
despite doing

./configure --with-sequencer=yes --with-oss=yes --with-cards=interwave

I think its something to do with the recent changes to
CONFIG_SND_SEQUENCER_OSS and CONFIG_SND_SEQUENCER.

Should CONFIG_SND_SEQUENCER_OSS have the value 'm' or 'y' or '1' ?
It seems to get the value of '1' from alsa-driver/include/config.h
the value of $(CONFIG_SND_SEQUENCER) (='m') in alsa-driver/Makefile.conf
yet in alsa-kernel/core/seq/oss/Makefile it is tested for value 'y'.

Problem 2:
==========
In alsa-lib, "automake --foreign --add-missing" drops out with
configure.in: 85: required file ynclude/config.h.in' not found

It was actually left in alsa-lib/config.h.in so I moved it to
alsa-lib/include/config.h.in by hand.

But later, autoconf drops out with
autoconf: Undefined macros:
configure.in:38:AC_DISABLE_STATIC
configure.in:39:AC_LIBTOOL_DLOPEN

I have autoconf-2.13 and automake-1.4 ... what versions are best for this?

Also, probably a minor thing, but in alsa-driver/support/Makefile
make complains about the last two lines:

make[2]: Entering directory `/u2/alsa-2002-05-24/alsa-driver/support'
Makefile:31: warning:
        overriding commands for target `snd-isapnp.o'
/u2/alsa-2002-05-24/alsa-driver/Rules.make:103: warning:
        ignoring old commands for target `snd-isapnp.o'

I just commented them out.

Ted.
-- 
Ted <[EMAIL PROTECTED]>
   http://www.nowtsfree.freeserve.co.uk

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to