From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000379]: necessary file backed out in update 3 months ago
Date: Tue, 9 Nov 2004 16:15:40 +0100 [thread overview]
Message-ID: <50ce251bccf88041c3586b8cbeb4cd8c@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=379>
======================================================================
Reported By: ndbusek
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 379
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Distribution:
Kernel Version:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 07-13-2004 03:38 CEST
Last Modified: 11-09-2004 16:15 CET
======================================================================
Summary: necessary file backed out in update 3 months ago
Description:
compiling vxp440.c fails with
vxpocket.c: File not found
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
has duplicate 0000368 vxpocket.c missing from 1.0.5 releases
======================================================================
----------------------------------------------------------------------
perex - 09-07-04 16:35
----------------------------------------------------------------------
This patch will solve your problem.
Index: Makefile
===================================================================
RCS file: /cvsroot/alsa/alsa-driver/pcmcia/vx/Makefile,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- Makefile 7 Apr 2004 17:53:41 -0000 1.10
+++ Makefile 7 Sep 2004 14:33:48 -0000 1.11
@@ -14,4 +14,5 @@
include $(SND_TOPDIR)/Rules.make
vxpocket.c: vxpocket.patch
$(SND_TOPDIR)/alsa-kernel/pcmcia/vx/vxpocket.c
+vxp440.c: vxpocket.c
vx_entry.c: vx_entry.patch vx_entry.inc vx_entry.inc1
$(SND_TOPDIR)/alsa-kernel/pcmcia/vx/vx_entry.c
Issue History
Date Modified Username Field Change
======================================================================
07-13-04 03:38 ndbusek New Issue
09-07-04 16:35 perex Status assigned => resolved
09-07-04 16:35 perex Resolution open => fixed
09-07-04 16:35 perex Note Added: 0001709
09-07-04 16:40 perex Relationship added has duplicate 0000368
11-09-04 16:15 tiwai Status resolved => closed
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next reply other threads:[~2004-11-09 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 15:15 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-07 14:35 [ALSA - driver 0000379]: necessary file backed out in update 3 months ago bugtrack
2004-07-13 1:38 noreply
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=50ce251bccf88041c3586b8cbeb4cd8c@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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 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.