From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [xf86-video-intel PATCH] build: do not use AC_CHECK_FILE to find the header files.
Date: Mon, 30 May 2011 09:27:09 +0100 [thread overview]
Message-ID: <013811$8t8jc@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1305418652-14402-1-git-send-email-flameeyes@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
On Sun, 15 May 2011 02:17:32 +0200, Diego Elio Pettenò <flameeyes@gmail.com> wrote:
> Using AC_CHECK_FILE will cause cross-builds to fail picking the right file;
> instead use compile/preprocessor checks properly, and check for
> xf86driproto earlier.
Applied with:
Reviewed-by: Rémi Cardona <remi@gentoo.org>
Thanks,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2011-05-30 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 0:17 [xf86-video-intel PATCH] build: do not use AC_CHECK_FILE to find the header files Diego Elio Pettenò
2011-05-30 8:27 ` Chris Wilson [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='013811$8t8jc@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox