All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Huddleston <jeremyhu@freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: libdrm fails 'make check' in tinderbox (was Re: [ANNOUNCE] libdrm 2.4.30)
Date: Sun, 29 Jan 2012 09:58:36 -0800	[thread overview]
Message-ID: <595BCDCE-D20D-4C80-8F41-3B7F1CC9AE5D@freedesktop.org> (raw)
In-Reply-To: <CAKMK7uF0giy2Xi1Fsnovuj2zLcB2R5kWTyuvgz11UzogoKEebQ@mail.gmail.com>

Ok, well I'll give it a shot then.  I've dealt with enough autoconf to make a decent first pass.

On Jan 29, 2012, at 04:16, Daniel Vetter wrote:

> On Sun, Jan 29, 2012 at 04:30, Jeremy Huddleston
> <jeremyhu@freedesktop.org> wrote:
>> Maybe I'm missing something here...
>> 
>> Shouldn't I be able to build and test support for Intel even if I've got an nVidia card in my box now?  Or is this support for Intel CPUs rather than Intel GPUs?
> 
> The issue is that we pretty much assume that the code runs on a
> little-endian machine - which is the reason the tests are failing for
> you on ppc. I'm with Eric that the most sensible thing to do here is
> to disable building the intel libdrm (and runnning its test) entirely
> on anything not x86 or from intel. My autofu isn't really up to snuff
> for that though :(
> -Daniel
> -- 
> Daniel Vetter
> daniel.vetter@ffwll.ch - +41 (0) 79 365 57 48 - http://blog.ffwll.ch
> 

  reply	other threads:[~2012-01-29 17:58 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 [this message]
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

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=595BCDCE-D20D-4C80-8F41-3B7F1CC9AE5D@freedesktop.org \
    --to=jeremyhu@freedesktop.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@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 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.