From: Daniel Vetter <daniel@ffwll.ch>
To: Matt Turner <mattst88@gmail.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
Ben Widawsky <ben@bwidawsk.net>,
Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH intel-gpu-tools] configure: Don't bail if libdrm_nouveau isn't available.
Date: Fri, 11 Oct 2013 23:24:09 +0200 [thread overview]
Message-ID: <20131011212409.GI8303@phenom.ffwll.local> (raw)
In-Reply-To: <CAEdQ38G7GSHdvuGL20hGfWCd5vBwSUmM-BrQuRXEvWn2_31gaA@mail.gmail.com>
On Fri, Oct 11, 2013 at 12:51:34PM -0700, Matt Turner wrote:
> On Fri, Oct 11, 2013 at 12:40 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Fri, Oct 11, 2013 at 5:56 AM, Matt Turner <mattst88@gmail.com> wrote:
> >> We were seriously *requiring* libdrm_nouveau unless explicitly disabled?
> >
> > I've had a bit of hilarious fail with optional testcases that
> > automatically get disabled when depencies aren't around. Hence why
> > they're all required by default with the optional switch to disable
> > them.
>
> You've had this problem in general, or with nouveau?
In general.
> I mean, this is kind of how autotools is supposed to work. If you
> explicitly want to ensure something is built you add --enable-thing.
Yeah, but otoh I'm positively incompetent ;-) And since the main use case
for i-g-t is to distribute the tests autoconf doesn't quite work like it
usually does.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-10-11 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 3:56 [PATCH intel-gpu-tools] configure: Don't bail if libdrm_nouveau isn't available Matt Turner
2013-10-11 4:00 ` Ben Widawsky
2013-10-11 7:40 ` Daniel Vetter
2013-10-11 19:51 ` Matt Turner
2013-10-11 21:24 ` Daniel Vetter [this message]
2013-10-11 21:29 ` Matt Turner
2013-10-11 22:51 ` Chad Versace
2013-10-11 22:52 ` Chad Versace
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=20131011212409.GI8303@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mattst88@gmail.com \
/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