From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000703]: alsa-driver-1.0.7 compile error dealing with 'remap_page_range'
Date: Fri, 3 Dec 2004 21:11:22 +0100 [thread overview]
Message-ID: <aef69cc8e5d30629cbff1bf5d2ea2d8b@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=703>
======================================================================
Reported By: Nsane457
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 703
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: Gentoo 2004.3
Kernel Version: linux-2.6.9-nitro4 (also tried mm-sources and
gentoo-dev-sources)
======================================================================
Date Submitted: 12-03-2004 21:00 CET
Last Modified: 12-03-2004 21:11 CET
======================================================================
Summary: alsa-driver-1.0.7 compile error dealing with
'remap_page_range'
Description:
Since I have a crappy OEM Dell SBLive! soundcard I can't use the emu10k1
module. I need the emu10k1x module which is now supported in alsa but not
in any kernel. I followed the instructions from
http://gentoo-wiki.com/HOWTO_ALSA_sound_mixer_aka_dmix . But no matter
what it won't compile. I changed the ALSA_CARDS variable to other cards,
and just one card, and it won't work.
======================================================================
----------------------------------------------------------------------
rlrevell - 12-03-04 21:11
----------------------------------------------------------------------
That sounds like an incorrect build procedure. You compile ALSA like
this:
./configure --with-cards=emu10k1x --with-kernel=/path/to/kernel/source
Issue History
Date Modified Username Field Change
======================================================================
12-03-04 21:00 Nsane457 New Issue
12-03-04 21:00 Nsane457 File Added: 2299-alsa-driver-1.0.7-r1.log
12-03-04 21:00 Nsane457 Distribution => Gentoo 2004.3
12-03-04 21:00 Nsane457 Kernel Version => linux-2.6.9-nitro4
(also tried mm-sources and gentoo-dev-sources)
12-03-04 21:03 Nsane457 File Added: straceinfo.log
12-03-04 21:11 rlrevell Note Added: 0002713
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next reply other threads:[~2004-12-03 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 20:11 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-19 15:50 [ALSA - driver 0000703]: alsa-driver-1.0.7 compile error dealing with 'remap_page_range' bugtrack
2004-12-16 17:43 bugtrack
2004-12-07 5:47 bugtrack
2004-12-06 20:51 bugtrack
2004-12-06 19:51 bugtrack
2004-12-06 10:01 bugtrack
2004-12-03 23:53 bugtrack
2004-12-03 20:00 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=aef69cc8e5d30629cbff1bf5d2ea2d8b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox