From: Takashi Iwai <tiwai@suse.de>
To: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
alsa-devel@alsa-project.org
Subject: Re: cvs not compiling cleanly
Date: Fri, 31 May 2002 10:35:08 +0200 [thread overview]
Message-ID: <s5hvg94hg03.wl@alsa2.suse.de> (raw)
In-Reply-To: <3CF6ED9E.D49C9B5F@boosthardware.com>
At Fri, 31 May 2002 12:27:26 +0900,
Patrick Shirkey wrote:
>
> Fernando Pablo Lopez-Lezcano wrote:
> >
> > Hi, today's cvs, fresh download. Not all modules are compiled
> > when doing a cvscompile from scratch. Last ones are the usb
> > modules, the whole pci directory is apparently skipped. The
> > final depmod also fails (maybe because there are modules
> > missing?):
> >
> > /sbin/depmod -a -e -b /var/tmp/alsa-driver-root/ 2.4.18-8.llsmp
> > depmod: *** Unresolved symbols in
...
> >
> > CVS from 2002-05-15.10:15:43 compiles fine on the same machine.
> > -- Fernando
> >
>
> I get a similar problem with the sequencer support for the cmipci. It
> has been like that since Monday AFAICR.
sorry, my mistake. i hope it's now fixed on cvs.
please give a try.
Takashi
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
next prev parent reply other threads:[~2002-05-31 8:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 15:14 snd_pcm_close hangs Tim Goetze
2002-05-30 23:19 ` cvs not compiling cleanly Fernando Pablo Lopez-Lezcano
2002-05-31 3:27 ` Patrick Shirkey
2002-05-31 8:35 ` Takashi Iwai [this message]
2002-05-31 8:42 ` snd_pcm_close hangs Takashi Iwai
2002-05-31 17:06 ` Tim Goetze
2002-05-31 23:49 ` Tim Goetze
2002-06-01 0:57 ` Tim Goetze
2002-06-01 11:22 ` Tim Goetze
2002-06-03 13:36 ` Takashi Iwai
2002-06-03 14:47 ` Tim Goetze
2002-06-03 17:48 ` Tim Goetze
2002-06-04 17:05 ` Takashi Iwai
2002-06-04 21:10 ` Tim Goetze
2002-06-10 14:22 ` 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=s5hvg94hg03.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=nando@ccrma.Stanford.EDU \
--cc=pshirkey@boosthardware.com \
/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.