From: Alan Coopersmith <alan.coopersmith@oracle.com>
To: Julien Cristau <jcristau@debian.org>
Cc: Jeremy Huddleston <jeremyhu@freedesktop.org>,
dri-devel@lists.freedesktop.org, daniel.vetter@ffwll.ch
Subject: Re: [PATCH] Don't build Intel DRM if $CHOST is not i?86-* or x86_64-*
Date: Wed, 01 Feb 2012 14:04:52 -0800 [thread overview]
Message-ID: <4F29B704.2010106@oracle.com> (raw)
In-Reply-To: <20120201215607.GO19118@radis.cristau.org>
On 02/ 1/12 01:56 PM, Julien Cristau wrote:
> On Wed, Feb 1, 2012 at 13:01:58 -0800, Jeremy Huddleston wrote:
>
>> yeah, that's probably cleaner (I guess it'll avoid the -*), but it should have the same effect.
>>
> I get host_os=linux-gnu here afaict, so not really the same effect, no.
Jeremy was probably thinking of $host, which has both the os & cpu in,
but this was already fixed in libdrm git last night when people on IRC
noticed that the Intel drm module stopped building on x86 systems.
commit 82c6938d232327233caac743a07639ac91bceb7e
Author: Paul Berry <stereotype441@gmail.com>
Date: Tue Jan 31 14:44:14 2012 -0800
intel: Fix build of Intel DRM on x86 systems
Commit efd6e81e inadvertently broke the build by looking for "i?86" or
"x86_64" in $host_os. The correct variable to check is $host_cpu.
This was preventing libdrm_intel.so from being built.
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
diff --git a/configure.ac b/configure.ac
index f5ebc1d..b59bc54 100644
--- a/configure.ac
+++ b/configure.ac
@@ -250,8 +250,8 @@ if test "x$INTEL" != "xno" -o "x$RADEON" != "xno"; then
else
if test "x$INTEL" != "xno"; then
- case $host_os in
- i?86-*|x86_64-*) INTEL=yes ;;
+ case $host_cpu in
+ i?86|x86_64) INTEL=yes ;;
*) INTEL=no ;;
esac
fi
--
-Alan Coopersmith- alan.coopersmith@oracle.com
Oracle Solaris Platform Engineering: X Window System
prev parent reply other threads:[~2012-02-01 22:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 16:54 libdrm 2.4.30 Eric Anholt
2012-01-07 19:22 ` [ANNOUNCE] " Jeremy Huddleston
2012-01-08 2:49 ` Eric Anholt
2012-01-08 8:48 ` Jeremy Huddleston
2012-01-09 16:15 ` Eric Anholt
2012-01-28 20:57 ` libdrm fails 'make check' in tinderbox (was Re: [ANNOUNCE] libdrm 2.4.30) Jeremy Huddleston
2012-01-29 1:55 ` Eric Anholt
2012-01-29 3:30 ` Jeremy Huddleston
2012-01-29 12:16 ` Daniel Vetter
2012-01-29 17:58 ` Jeremy Huddleston
2012-01-30 16:26 ` Eric Anholt
2012-01-30 23:25 ` [PATCH] Don't build Intel DRM if $CHOST is not i?86-* or x86_64-* Jeremy Huddleston
2012-01-31 16:59 ` Eric Anholt
2012-01-31 18:34 ` Jeremy Huddleston
2012-01-31 21:12 ` Eric Anholt
2012-02-01 20:43 ` Julien Cristau
2012-02-01 21:01 ` Jeremy Huddleston
2012-02-01 21:56 ` Julien Cristau
2012-02-01 21:59 ` Jeremy Huddleston
2012-02-01 22:04 ` Alan Coopersmith [this message]
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=4F29B704.2010106@oracle.com \
--to=alan.coopersmith@oracle.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jcristau@debian.org \
--cc=jeremyhu@freedesktop.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.