Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ivica Bukvic" <ico@fuse.net>
To: 'Paul Davis' <pbd@op.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: RE: Failed to compile HDSP driver from the CVS
Date: Tue, 14 May 2002 09:30:17 -0400	[thread overview]
Message-ID: <000601c1fb4b$7cd77ae0$ac1f830a@ico> (raw)
In-Reply-To: <200205141306.g4ED65T06570@post2.fast.net>

Thank you for your prompt reply!

However, this is the first time ever I tried using the CVS, so I had no
files hanging around prior to this downloading. I am also pretty sure
that I downloaded the stuff with -P flag (I did it as instructions on
the alsa-project page have stated it, including the -P flag). On top of
that I even tried updating the whole CVS tree just to see if that will
fix it.

So, I am not sure why it is even referencing the file in the first place
if none of the other files are supposed to mention it.

Should I uninstall every trace of Alsa from my cpu before trying to use
CVS?

Ico

> -----Original Message-----
> From: Paul Davis [mailto:pbd@op.net]
> Sent: Tuesday, May 14, 2002 9:07 AM
> To: Ivica Bukvic
> Cc: alsa-devel@alsa-project.org
> Subject: Re: Failed to compile HDSP driver from the CVS

> i think you failed to use the "-P" flag to the CVS update
> command. Always use this flag, otherwise when someone removes a file
> from CVS, its not removed from your local tree.
> 
> as a result, you've still got rme9652_mem.c hanging around, and the
> "fastdep" make target looks at *all* sources, not just those that are
> listed in the Makefile. you need to remove this file. there are two
> versions of it, one under alsa-kernel, one under alsa-driver.
> 
> please keep in mind that you should update alsa-lib and alsa-utils as
> well, because they have been modified to support the 64 bit register
> used by the H-DSP for its RMS meters.
> 
> --p



_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

  reply	other threads:[~2002-05-14 13:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14  6:51 Failed to compile HDSP driver from the CVS Ivica Bukvic
2002-05-14 13:07 ` Paul Davis
2002-05-14 13:30   ` Ivica Bukvic [this message]
2002-05-14 13:58     ` Paul Davis
2002-05-14 18:21       ` Jörn Nettingsmeier
2002-05-15 12:29       ` Maarten de Boer
2002-05-15 12:49         ` Paul Davis
  -- strict thread matches above, loose matches on Subject: below --
2002-05-14 22:16 Ivica Bukvic
2002-05-15  0:02 ` Paul Davis
2002-05-15  1:31   ` Ivica Bukvic
2002-05-14 22:19 Ivica Bukvic

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='000601c1fb4b$7cd77ae0$ac1f830a@ico' \
    --to=ico@fuse.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pbd@op.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox