Am Dienstag 06 April 2004 12:52 schrieb Karsten Wiese: > Am Dienstag 06 April 2004 02:10 schrieb Rui Nuno Capela: > > Now comes the weird part. No, I couldn't get it to work unless I set > > --with-debug=full on configure line. And I've tested several times, > > believe me. > > > > FYI, I'm stick with 2.6 kernel tree, and already tested with 2.6.4 and > > latest 2.6.5. > > > > My way of building the kernel modules is from stock tarball, and is > > pretty canonical, as literally as follows (all as root): > > > > tar -jxf alsa-driver-1.0.4.tar.bz2 > > cd alsa-driver-1.0.4 > > gzip -dc ../alsa-driver-1.0.4p1.patch.gz # see attachment > > ./configure --with-isapnp=no --with-sequencer=yes --with-oss=yes > > --with-cards=all --with-debug=full > > make > > make install > > > > As stated, the INPUT MONITOR LED does not get lit if I take out the > > clause --with-debug=full. > > > > How come? > > You don't use --with-kernel option. > Are you shure ALSA build sees the correct linux-kernel source? > What distro are you using? > On some (i.e. fc1) you'd have to specify a special gcc like > export CC=gcc32 > befure ./configure. > I'm building a no debug ALSA here with a 2.6.5-aa1 kernel. > maybe I'll find something..... Yes, same odd behavior here: built without --with-debug=full, nothing is sent from us428control to the us428. So your build process is propably ok.
Cheers, Karsten ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
