Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: tomasz motylewski <T.Motylewski@bfad.de>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: rc4
Date: Wed, 23 Oct 2002 19:51:39 +0900	[thread overview]
Message-ID: <3DB67F3B.4090407@boosthardware.com> (raw)
In-Reply-To: Pine.LNX.4.21.0210231231440.321-100000@mailserver.intern.bfad.de

tomasz motylewski wrote:
> I have just updated to CVS.
> 
> Debian 2.2
> 
> I needed to run autoconf; ./configure; make; ./configure; make
> 
> cd alsa-driver
> 
> ./configure
> [...]
> checking for USB... no
> checking for PCMCIA... yes
> ./configure: ALSA_TOPLEVEL_INIT: command not found
> ./configure: ALSA_TOPLEVEL_SELECT: command not found
> updating cache ./config.cache
> creating ./config.status
> creating version
> creating Makefile.conf
> creating snddevices
> creating utils/alsa-driver.spec
> creating utils/buildrpm
> creating toplevel.config
> sed: can't read ./toplevel.config.in: No such file or directory
> creating include/config.h
> creating include/config1.h
> cat: ./include/config1.h.in: No such file or directory
> creating include/version.h
> tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ make
> make  all-deps
> make[1]: Entering directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'
> ln -sf ../alsa-kernel alsa-kernel
> gcc -Ialsa-kernel/scripts alsa-kernel/scripts/mod-deps.c -o utils/mod-deps
> cat alsa-kernel/scripts/Modules.dep utils/Modules.dep | utils/mod-deps
> --makeconf > toplevel.config.in
> cat alsa-kernel/scripts/Modules.dep utils/Modules.dep | utils/mod-deps
> --acinclude > acinclude.m4
> cat alsa-kernel/scripts/Modules.dep utils/Modules.dep | utils/mod-deps
> --include > include/config1.h.in
> make[1]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'
> 
> Please, run the configure script as first...
> tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ ./configure 
> loading cache ./config.cache
> [...]
> checking for USB... no
> checking for PCMCIA... yes
> ./configure: ALSA_TOPLEVEL_INIT: command not found
> ./configure: ALSA_TOPLEVEL_SELECT: command not found
> creating ./config.status
> creating version
> creating Makefile.conf
> creating snddevices
> creating utils/alsa-driver.spec
> creating utils/buildrpm
> creating toplevel.config
> creating include/config.h
> include/config.h is unchanged
> creating include/config1.h
> creating include/version.h
> include/version.h is unchanged
> tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ make
> if [ ! -d include/sound -a ! -L include/sound ]; then \
>   ln -sf ../alsa-kernel/include include/sound ; \
> fi
> cp -auvf include/version.h include/sound/version.h
> include/version.h -> include/sound/version.h
> make dep
> make[1]: Entering directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'
> make[2]: Entering directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore'
> make  -C ioctl32 fastdep
> make[3]: Entering directory
> `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore/ioctl32'
> /home/tom/devel/aeg/ALSA/cvs/alsa-driver/include/sndversions.h was updated
> gcc -M -D__KERNEL__ -DMODULE=1
> -I/home/tom/devel/aeg/ALSA/cvs/alsa-driver/include
> -I/lib/modules/2.4.9/build/include -O2 -mpreferred-stack-boundary=2 -march=i686
> -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD
> hwdep32.c ioctl32.c pcm32.c rawmidi32.c seq32.c timer32.c > .depend
> make[3]: Leaving directory
> `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore/ioctl32'
> make  -C oss fastdep
> make[3]: Entering directory
> `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore/oss'
> /home/tom/devel/aeg/ALSA/cvs/alsa-driver/include/sndversions.h was not updated
> gcc -D__KERNEL__ -DMODULE=1 -I/home/tom/devel/aeg/ALSA/cvs/alsa-driver/include
> -I/lib/modules/2.4.9/build/include -O2 -mpreferred-stack-boundary=2 -march=i686
> -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD  -E
> -D__GENKSYMS__ mixer_oss.c
> 
> - it sems to be OK at this point.
> 
> But then:
> 
> gcc -M -D__KERNEL__ -DMODULE=1
> -I/home/tom/devel/aeg/ALSA/cvs/alsa-driver/include
> -I/lib/modules/2.4.9/build/include -O2 -mpreferred-stack-boundary=2 -march=i686
> -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD
> gus_dma.c gus_dram.c gus_instr.c gus_io.c gus_irq.c gus_lfo.c gus_main.c
> gus_mem.c gus_mem_proc.c gus_mixer.c gus_pcm.c gus_reset.c gus_sample.c
> gus_simple.c gus_synth.c gus_timer.c gus_uart.c gus_volume.c gusclassic.c
> gusextreme.c gusmax.c interwave-stb.c interwave.c > .depend
> make[3]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/isa/gus'
> make  -C msnd fastdep
> make: Entering an unknown directory
> make: *** msnd: No such file or directory.  Stop.
> make: Leaving an unknown directory
> make[2]: *** [_sfdep_msnd] Error 2
> make[2]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/isa'
> make[1]: *** [dep] Error 1
> make[1]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'
> make: *** [include/sndversions.h] Error 2
> tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ 
> 
> 
> What is the "true one" method of compling ALSA CVS?
> 

It's in the online docs but for your convienience

./cvscompile --with-cards=snd-xxx;make;make install

where snd-xxx is the name of the module for your card.


-- 
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://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

  reply	other threads:[~2002-10-23 10:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23  7:57 rc4 lib - build failing Jaroslav Kysela
2002-10-23  8:37 ` m
2002-10-23  9:22   ` Jaroslav Kysela
2002-10-23  9:27     ` m
2002-10-23  9:44 ` Takashi Iwai
2002-10-23 10:06   ` Jaroslav Kysela
2002-10-23 10:23     ` Takashi Iwai
2002-10-23 10:37     ` rc4 tomasz motylewski
2002-10-23 10:51       ` Patrick Shirkey [this message]
2002-10-23 11:24         ` rc4 James Tappin
2002-10-23 11:38           ` rc4 m
2002-10-23 11:45           ` rc4 Takashi Iwai
2002-10-23 11:29       ` rc4 Takashi Iwai
2002-10-23 18:17         ` rc4 tomasz motylewski
2002-10-24 10:21           ` rc4 Takashi Iwai

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=3DB67F3B.4090407@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=T.Motylewski@bfad.de \
    --cc=alsa-devel@alsa-project.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