From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - tools 0000340]: Error in alsa-tools/seq/sbiload/Makefile.am
Date: Wed, 30 Jun 2004 16:06:39 +0200 [thread overview]
Message-ID: <8c53f8f9388cfef52b298166d921f3bc@bugtrack.alsa-project.org> (raw)
The following bug has been RESOLVED.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000340
======================================================================
Reported By: linus
Assigned To: tiwai
======================================================================
Project: ALSA - tools
Bug ID: 340
Category: firmware loaders
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Resolution: fixed
======================================================================
Date Submitted: 06-20-2004 09:55 CEST
Last Modified: 06-30-2004 16:06 CEST
======================================================================
Summary: Error in alsa-tools/seq/sbiload/Makefile.am
Description:
In the alsa-tools module of the CVS, the seq/sbiload/Makefile.am has an
incomplete EXTRA_DIST line, omitting several important files that must be
included in the dist. tar.gz-files. It currently reads:
EXTRA_DIST = README COPYING depcomp
But shall read:
EXTRA_DIST = README COPYING depcomp drums.o3 drums.sb std.o3 std.sb
Or the instrument patches does not come with the install... Perhaps these
should also be:
sbiload_DATA = drums.o3 drums.sb std.o3 std.sb
or similar so that the instruments get installed in /usr/share or
similar.
(Not 100% about the syntax here right now.)
======================================================================
----------------------------------------------------------------------
tiwai - 06-30-2004 16:06 CEST
----------------------------------------------------------------------
fixed on cvs.
also, sbiload has a new option -P option to specify the patch path.
Bug History
Date Modified Username Field Change
======================================================================
06-20-04 09:55 linus New Bug
06-30-04 16:06 tiwai Bugnote Added: 0001354
06-30-04 16:06 tiwai Assigned To => tiwai
06-30-04 16:06 tiwai Resolution open => fixed
06-30-04 16:06 tiwai Status new => resolved
======================================================================
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next reply other threads:[~2004-06-30 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 14:06 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-16 10:56 [ALSA - tools 0000340]: Error in alsa-tools/seq/sbiload/Makefile.am noreply
2004-06-20 7:55 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=8c53f8f9388cfef52b298166d921f3bc@bugtrack.alsa-project.org \
--to=noreply@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox