All of lore.kernel.org
 help / color / mirror / Atom feed
From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000358]: error in pcm_native.c while compiling alsa-driver from cvs
Date: Wed, 30 Jun 2004 23:46:40 +0200	[thread overview]
Message-ID: <7ad06419a6f9ee6d868b2314f1d050fd@bugtrack.alsa-project.org> (raw)


The following bug has been SUBMITTED.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000358
======================================================================
Reported By:                msrinath80
Assigned To:                perex
======================================================================
Project:                    ALSA - driver
Bug ID:                     358
Category:                   0_compilation problem_!!!
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Distribution:               RedHat Linux 9
Kernel Version:             2.4.20-8
======================================================================
Date Submitted:             06-30-2004 23:46 CEST
Last Modified:              06-30-2004 23:46 CEST
======================================================================
Summary:                    error in pcm_native.c while compiling alsa-driver
from cvs
Description: 
When I try to do a ./cvscompile --with-cards=emu10k1x for a fresh Check Out
(30th June) from alsa CVS, I get the following error:
---------------
pcm_native.c: In function `snd_pcm_mmap_data':
pcm_native.c:3176: warning: passing arg 1 of `remap_page_range' makes
pointer from integer without a cast
pcm_native.c:3176: incompatible type for argument 4 of `remap_page_range'
pcm_native.c:3176: too few arguments to function `remap_page_range'
make[1]: *** [pcm_native.o] Error 1
make[1]: Leaving directory `/home/srinath/alsacvs/alsa-driver/acore'
make: *** [compile] Error 1
---------------
======================================================================

Bug History
Date Modified  Username       Field                    Change              
======================================================================
06-30-04 23:46 msrinath80     New Bug                                      
06-30-04 23:46 msrinath80     File Added: log                              
06-30-04 23:46 msrinath80     Distribution              => RedHat Linux 9  
06-30-04 23:46 msrinath80     Kernel Version            => 2.4.20-8        
======================================================================




-------------------------------------------------------
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

             reply	other threads:[~2004-06-30 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 21:46 noreply [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-14  8:27 [ALSA - driver 0000358]: error in pcm_native.c while compiling alsa-driver from cvs noreply
2004-07-15  9:22 noreply
2004-09-24 11:35 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=7ad06419a6f9ee6d868b2314f1d050fd@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 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.