-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


make[3]: Entering directory `/root/alsa-driver/acore/ioctl32'
/root/alsa-driver/include/sndversions.h was updated
gcc -M -D__KERNEL__ -DMODULE=1 -I/root/alsa-driver/include
@EXTRA_INCLUDES@ -I/l
ib/modules/2.4.20-ac1/build/include -O2 -mpreferred-stack-boundary=2
- -march=i686
 -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD
hwde
p32.c ioctl32.c pcm32.c rawmidi32.c seq32.c timer32.c > .depend
gcc: @EXTRA_INCLUDES@: No such file or directory
make[3]: *** [fastdep] Error 1
make[3]: Leaving directory `/root/alsa-driver/acore/ioctl32'
make[2]: *** [_sfdep_ioctl32] Error 2
make[2]: Leaving directory `/root/alsa-driver/acore'
make[1]: *** [dep] Error 1
make[1]: Leaving directory `/root/alsa-driver'
make: *** [include/sndversions.h] Error 2

something not right in cvs version?

- -asher

On Thu, 12 Dec 2002, Takashi Iwai wrote:

> At Wed, 11 Dec 2002 14:37:10 -0500 (EST),
> Asher Yanich wrote:
> >
> >
> > subject says it, Redhat 8.0, pcmcia-cs 3.2.3, not using kernel pcmcia.  I
> > run configure and it does not detect PCMCIA so it does not build
> > pcmcia/vx/*
> >
> > any suggestions?  I would really like to beta test these drivers?
>
> the cvs version of alsa-driver has now --with-pcmcia and
> --with-pcmcia-root options.  you can specify like
>
>       % ./configure --with-pcmcia=external \
>               --with-pcmcia-root=/somewhere/pcmcia-cs-xxx
>
> please give a try.
>
>
> Takashi
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE9+ToLAvdNfNYuUt8RAmESAJ9vHer6pCFb8C0f9I/xny2VgU3qgwCcDogi
iZc1Jw2f5Zm+BrYQw+QTCSU=
=kgiJ
-----END PGP SIGNATURE-----



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to