From: Patrick Shirkey <pshirkey@boosthardware.com>
To: m <m@iriXx.org>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: problems compiling from cvs
Date: Wed, 23 Oct 2002 04:52:44 +0900 [thread overview]
Message-ID: <3DB5AC8C.4030905@boosthardware.com> (raw)
In-Reply-To: 1035314317.3100.4.camel@hamish.iriXx.org
m wrote:
> hi,
>
> i was directed to this list by Patrick Shirkey who suggested that i
> might be able to help with testing the midi support for the usb audio
> quattro... i'm also testing an Evolution UC-16 for a magazine review...
>
> i've downloaded a copy of rc4 from cvs, but am getting the following
> errors on doing
> make ALSAKERNELDIR=../alsa-kernel
>
> gcc -D__KERNEL__ -DMODULE=1 -I/home/miriam/alsa-driver/include
> -I/lib/modules/2.4.18-6mdk/build/include -O2
> -mpreferred-stack-boundary=2 -march=i586 -DLINUX -Wall
> -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD
> -DEXPORT_SYMTAB -c seq_instr.c
> In file included from ../../alsa-kernel/core/seq/seq_instr.c:25,
> from seq_instr.c:1:
> ../../alsa-kernel/core/seq/seq_clientmgr.h:56: parse error before
> `bitmap_member'
> ../../alsa-kernel/core/seq/seq_clientmgr.h:56: warning: no semicolon at
> end of struct or union
> ../../alsa-kernel/core/seq/seq_clientmgr.h:73: parse error before `}'
> make[2]: *** [seq_instr.o] Error 1
> make[2]: Leaving directory `/home/miriam/alsa-driver/acore/seq'
> make[1]: *** [_modsubdir_seq] Error 2
> make[1]: Leaving directory `/home/miriam/alsa-driver/acore'
> make: *** [compile] Error 1
>
> if anyone could help in interpreting what may be missing here i would be
> very grateful,
>
You only need to compile alsa-devel, alsa-lib and alsa-utils
for alsa-devel use
./cvscompile --with-cards=usb-audio --with-sequencer=yes;make;make install
then run ./snddevices
for the other two
./cvscompile;make;make install
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote
prev parent reply other threads:[~2002-10-22 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 19:18 problems compiling from cvs m
2002-10-22 19:52 ` Patrick Shirkey [this message]
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=3DB5AC8C.4030905@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=m@iriXx.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox