All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Fleury <fleury@cs.auc.dk>
To: alsa-devel@lists.sourceforge.net
Subject: sscape_ioctl.h not found!
Date: Mon, 23 Sep 2002 19:05:54 +0200	[thread overview]
Message-ID: <3D8F49F2.7030607@cs.auc.dk> (raw)

Hi,

I get the last CVS snapshot (from today) of alsa-driver
and I try to compile it on my new machine with a 2.4.19
kernel.

At the beginning, I had hard to figure out that the
directory alsa-kernel was missing.

Ok, I get it from the rc3 release.

Then, I tried the following command line:
./cvscompile --with-cards=cmipci --with-sequencer=yes --with-oss=yes 
-with-isapnp=no --with-debug=none

But then, during the dependencies building, I get:

gcc -M -D__KERNEL__ -DMODULE=1 
-I/home/fleury/install/src/alsa-driver/include 
-I/lib/modules/2.4.19custom/build/include -O2 
-mpreferred-stack-boundary=2 -march=i686 -DLINUX -Wall 
-Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD  als100.c 
azt2320.c cmi8330.c dt019x.c es18xx.c opl3sa2.c sgalaxy.c sscape.c > .depend
sscape.c:41: sound/sscape_ioctl.h: No such file or directory
make[1]: *** [fastdep] Error 1
make[1]: Leaving directory `/home/fleury/install/src/alsa-driver/isa'
make: *** [dep] Error 1

Actually, I didn't find any sound/sscape_ioctl.h anywhere... :-/

Did I miss something ?

Regards
-- 
Emmanuel

Most of my cliches aren't original.
   -- Chuck Knox, NFL football coach



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

             reply	other threads:[~2002-09-23 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 17:05 Emmanuel Fleury [this message]
2002-09-23 19:03 ` sscape_ioctl.h not found! Martin Langer
2002-09-23 19:12   ` Emmanuel Fleury

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D8F49F2.7030607@cs.auc.dk \
    --to=fleury@cs.auc.dk \
    --cc=alsa-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.