All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001977]: Compilation fails due to bad configuration step
Date: Wed, 29 Mar 2006 18:52:57 +0200	[thread overview]
Message-ID: <1f00a5b344e41aa4a084897bc72172da@bugtrack.alsa-project.org> (raw)


The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1977> 
======================================================================
Reported By:                Faber
Assigned To:                perex
======================================================================
Project:                    ALSA - driver
Issue ID:                   1977
Category:                   0_compilation problem_!!!
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Distribution:               
Kernel Version:             
Resolution:                 fixed
Fixed in Version:           
======================================================================
Date Submitted:             03-29-2006 15:43 CEST
Last Modified:              03-29-2006 18:52 CEST
======================================================================
Summary:                    Compilation fails due to bad configuration step
Description: 
Configure detects Via C3-2 system as "unknown", causing incorrect detection
of vmalloc_to_page, pci_saved_config, new_pci_save_state. This causes
compilation to fail.
======================================================================

----------------------------------------------------------------------
 tiwai - 03-29-06 18:52 
----------------------------------------------------------------------
The pactch is applied to CVS.  Thanks.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
03-29-06 15:43 Faber          New Issue                                    
03-29-06 15:43 Faber          File Added: c3_2_configure.patch                  
 
03-29-06 15:53 Faber          Issue Monitored: Faber                       
03-29-06 18:52 tiwai          Status                   assigned => resolved
03-29-06 18:52 tiwai          Resolution               open => fixed       
03-29-06 18:52 tiwai          Note Added: 0009002                          
======================================================================




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

             reply	other threads:[~2006-03-29 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 16:52 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-29 13:43 [ALSA - driver 0001977]: Compilation fails due to bad configuration step 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=1f00a5b344e41aa4a084897bc72172da@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.