From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000002]: 1.0.2: intel8x0.c build problem
Date: Tue, 27 Jan 2004 20:48:09 +0100 (CET) [thread overview]
Message-ID: <20040127194809.3556C21003@server.perex-int.cz> (raw)
The following bug has been CLOSED
======================================================================
http://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=0000002
======================================================================
Reporter: ZlatkO
Handler:
======================================================================
Project: ALSA - driver
Bug ID: 2
Category: PCI - intel8x0
Reproducibility: always
Severity: block
Priority: normal
Status: closed
Distribution: Slackware 8.1
Kernel Version: 2.4.24
======================================================================
Date Submitted: 01-27-2004 20:11 CET
Last Modified: 01-27-2004 20:48 CET
======================================================================
Summary: 1.0.2: intel8x0.c build problem
Description:
alsa-driver-1.0.2 doesn't build out of the box with gcc-2.95.3. The
attached patch fixes the problem.
======================================================================
----------------------------------------------------------------------
perex - 01-27-2004 20:47 CET
----------------------------------------------------------------------
I have regenerated the alsa-driver package with this fix.
It is dated:
Jan 27 14:15 alsa-driver-1.0.2.tar.bz2
----------------------------------------------------------------------
perex - 01-27-2004 20:48 CET
----------------------------------------------------------------------
The updated package is available at the ALSA FTP site.
Bug History
Date Modified Username Field Change
======================================================================
01-27-04 20:11 ZlatkO New Bug
01-27-04 20:11 ZlatkO File Added: alsa-driver-1.0.2.diff
01-27-04 20:47 perex Bugnote Added: 0000002
01-27-04 20:48 perex Bugnote Added: 0000003
01-27-04 20:48 perex Status new => closed
======================================================================
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next reply other threads:[~2004-01-27 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 19:48 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-27 19:47 [ALSA - driver 0000002]: 1.0.2: intel8x0.c build problem noreply
2004-01-27 19:11 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=20040127194809.3556C21003@server.perex-int.cz \
--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 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.