From: Paul Davis <pbd@op.net>
To: Ivica Bukvic <ico@fuse.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Failed to compile HDSP driver from the CVS
Date: Tue, 14 May 2002 20:02:28 -0400 [thread overview]
Message-ID: <200205150001.g4F012T12698@post2.fast.net> (raw)
In-Reply-To: Your message of "14 May 2002 18:16:27 EDT." <1021414588.4152.1.camel@badass-bukvic.dyndns.org>
>I am a bit confused. It is not the fact that I do have this file, but
>that the compile was looking for it. It must have been that issue you
>mentioned about CVS being not up-to-date.
its a combination of the "fastdep" target looking at *all* existing
sources, whether they are meant to be there or not, plus the CVS sync issue.
However, here's the error when
>I try to compile the driver now, after updating it with
use cvscompile to build it, i think.
--p
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
next prev parent reply other threads:[~2002-05-15 0:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 22:16 Failed to compile HDSP driver from the CVS Ivica Bukvic
2002-05-15 0:02 ` Paul Davis [this message]
2002-05-15 1:18 ` unresolved symbols, cvs, hammerfall Fernando Pablo Lopez-Lezcano
2002-05-15 1:31 ` Failed to compile HDSP driver from the CVS Ivica Bukvic
2002-05-15 1:39 ` Failed to compile HDSP driver from the CVS -- solution? Ivica Bukvic
2002-05-15 2:11 ` HDSP -- how to configure modules.conf? Ivica Bukvic
2002-05-15 12:41 ` Paul Davis
2002-05-15 17:22 ` Ivica Bukvic
2002-05-15 17:27 ` Paul Davis
-- strict thread matches above, loose matches on Subject: below --
2002-05-14 22:19 Failed to compile HDSP driver from the CVS Ivica Bukvic
2002-05-14 6:51 Ivica Bukvic
2002-05-14 13:07 ` Paul Davis
2002-05-14 13:30 ` Ivica Bukvic
2002-05-14 13:58 ` Paul Davis
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=200205150001.g4F012T12698@post2.fast.net \
--to=pbd@op.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ico@fuse.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.