From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0001579]: code.c test uses x86 asm, it should be x86/amd64 only
Date: Mon, 2 Jan 2006 19:28:56 +0100 [thread overview]
Message-ID: <69b7ffd6e3be3f0bd41f8c99487db2c2@bugtrack.alsa-project.org> (raw)
The issue 0001701 has been removed as a DUPLICATE OF the following issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1579>
======================================================================
Reported By: Flameeyes
Assigned To: tiwai
======================================================================
Project: ALSA - lib
Issue ID: 1579
Category: 0_general
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 11-19-2005 20:17 CET
Last Modified: 11-23-2005 17:36 CET
======================================================================
Summary: code.c test uses x86 asm, it should be x86/amd64
only
Description:
As per summary, the code.c test can't be built for any other system but x86
or amd64, as it uses inline asm focused on i386.
The attached patch makes it conditional to those arches.
HTH,
Diego
======================================================================
----------------------------------------------------------------------
tiwai - 11-23-05 17:34
----------------------------------------------------------------------
It's easier just to remove code from check_PROGRAMS. It's nothing but a
test code for dmix, and shouldn't be used as "check".
----------------------------------------------------------------------
tiwai - 11-23-05 17:36
----------------------------------------------------------------------
Fixed on CVS.
Issue History
Date Modified Username Field Change
======================================================================
11-19-05 20:17 Flameeyes New Issue
11-19-05 20:17 Flameeyes File Added: alsa-lib-1.0.10-test-ppc.patch
11-23-05 17:34 tiwai Note Added: 0006817
11-23-05 17:36 tiwai Status new => resolved
11-23-05 17:36 tiwai Resolution open => fixed
11-23-05 17:36 tiwai Assigned To => tiwai
11-23-05 17:36 tiwai Note Added: 0006818
01-02-06 19:28 rlrevell Relationship added has duplicate 0001701
01-02-06 19:28 rlrevell Relationship deleted has duplicate 0001701
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-02 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 18:28 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-02 18:28 [ALSA - lib 0001579]: code.c test uses x86 asm, it should be x86/amd64 only bugtrack
2005-11-23 16:36 bugtrack
2005-11-23 16:34 bugtrack
2005-11-19 19:17 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=69b7ffd6e3be3f0bd41f8c99487db2c2@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