From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001934]: make problem
Date: Mon, 10 Apr 2006 18:38:59 +0200 [thread overview]
Message-ID: <0197fb6faba88d3b656a5d0f4ea67886@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1934>
======================================================================
Reported By: kvo
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 1934
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
Distribution: RHEL4 Update 3
Kernel Version: 2.6.9-34.EL
======================================================================
Date Submitted: 03-17-2006 12:19 CET
Last Modified: 04-10-2006 18:38 CEST
======================================================================
Summary: make problem
Description:
./configure works OK. running make give error during compilation: module
'include/asound.h' (line 210) has some 'typedef' that doesn't match with
(probably) OS include. As a result, compilation stops and driver can not
be produced.
======================================================================
----------------------------------------------------------------------
tiwai - 04-10-06 16:46
----------------------------------------------------------------------
Sigh, it's a modified kernel by RedHat that not supported officially by
alsa package.
I don't know how to detect it.
----------------------------------------------------------------------
kvo - 04-10-06 18:38
----------------------------------------------------------------------
I understand your reason, but 1) RedHat is one of two major distributions,
and not taking it into account will seriously restrict ALSA scope; 2) I
had the similar results for SuSE 10.0 (not OpenSuSE), but, in this case, I
don't need compile ALSA myself, I could use packman ...
Issue History
Date Modified Username Field Change
======================================================================
03-17-06 12:19 kvo New Issue
03-17-06 12:19 kvo Distribution => RHEL4 Update 3
03-17-06 12:19 kvo Kernel Version => 2.6.9-34.EL
03-17-06 12:25 tiwai Note Added: 0008643
03-19-06 22:26 kvo Note Added: 0008697
03-21-06 17:33 tiwai Note Added: 0008749
03-25-06 20:47 kvo File Added: config.log
03-25-06 22:19 kvo Note Added: 0008952
04-09-06 18:47 kvo File Added: info.zip
04-09-06 18:56 kvo Note Added: 0009181
04-09-06 19:05 kvo Issue Monitored: tiwai
04-09-06 19:05 kvo Note Added: 0009182
04-10-06 16:46 tiwai Note Added: 0009196
04-10-06 18:38 kvo Note Added: 0009213
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-04-10 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 16:38 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-30 9:48 [ALSA - driver 0001934]: make problem bugtrack
2006-04-30 4:04 bugtrack
2006-04-21 3:39 bugtrack
2006-04-20 22:03 bugtrack
2006-04-10 16:43 bugtrack
2006-04-10 14:46 bugtrack
2006-04-09 16:56 bugtrack
2006-03-25 21:19 bugtrack
2006-03-21 16:33 bugtrack
2006-03-19 21:26 bugtrack
2006-03-17 11:25 bugtrack
2006-03-17 11:19 bugtrack
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=0197fb6faba88d3b656a5d0f4ea67886@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.