From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000658]: processor detection in configure.in breaks detection of kernel config options
Date: Fri, 19 Nov 2004 12:13:32 +0100 [thread overview]
Message-ID: <30cdf8018c6034f093776b6b96a0cd76@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=658>
======================================================================
Reported By: eradicator
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 658
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Distribution: Gentoo
Kernel Version: 2.6.7
======================================================================
Date Submitted: 11-19-2004 12:13 CET
Last Modified: 11-19-2004 12:13 CET
======================================================================
Summary: processor detection in configure.in breaks detection
of kernel config options
Description:
The location of the processor detection code in configure.in needs to be
moved to the end of configure.in after all calls to CHECK_KERNEL_CONFIG
and AC_TRY_RUN. This is because the processor detection code changes CC
(which is used by CHECK_KERNEL_CONFIG) to the compiler used by kernel
compilation. The kernel compiler might not be able to make runable
binaries (such as when libc is not available for its target and thus
should not be used for AC_TRY_RUN (which is used by CHECK_KERNEL_CONFIG).
This was experienced on Gentoo/Sparc and resulted in kernel modules being
built for the wrong kernel configuration (such as not detecting procfs).
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
11-19-04 12:13 eradicator New Issue
11-19-04 12:13 eradicator File Added: alsa-driver-1.0.7-configure.patch
11-19-04 12:13 eradicator Distribution => Gentoo
11-19-04 12:13 eradicator Kernel Version => 2.6.7
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next reply other threads:[~2004-11-19 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 11:13 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-29 15:14 [ALSA - driver 0000658]: processor detection in configure.in breaks detection of kernel config options bugtrack
2004-12-29 13:32 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=30cdf8018c6034f093776b6b96a0cd76@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