Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Cyril Brulebois <kibi@debian.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] xf86-video-intel: Update autotools configuration
Date: Sat, 02 Apr 2011 10:47:34 +0100	[thread overview]
Message-ID: <849307$c9k6e3@azsmga001.ch.intel.com> (raw)
In-Reply-To: <20110330014329.GA31787@debian.org>

[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]

On Wed, 30 Mar 2011 03:43:29 +0200, Cyril Brulebois <kibi@debian.org> wrote:
> Hi again,
> 
> Cyril Brulebois <kibi@debian.org> (10/02/2011):
> > The commit message says:
> > | Update autotools configuration
> > | 
> > | Use new libtool syntax and silent-rules to silent
> > | the build output a bit (linux-like)
> > 
> > What it doesn't say is:
> > -AC_CONFIG_AUX_DIR(.)
> > +AC_CONFIG_AUX_DIR([build-aux])
> 
> sorry to get back to this, but it's actually a bit more annoying than
> just breaking tinderbox at the time. Out of the 56 X drivers I'm
> currently maintaining, that's the only one no longer searching in '.',
> and I don't know why that should be.
> 
> Also, “autoreconf -vfi” puts files there, but those aren't cleaned,
> even through targets like distclean or maintainer-clean. Having to
> clean things through “git clean -xdf” sounds like a no-no to me. (Of
> course, our build system is flexible enough that I can do anything,
> like rm -rf'ing that directory, but I'd rather not have to come to
> this kind of things…)

I am slightly perplexed by this, since the darn thing passed make
distcheck which I thought included a test to make sure that all files
were deleted after a make clean. Was I just naive in believing that was
sufficient?
-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

      reply	other threads:[~2011-04-02  9:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 11:30 [PATCH] xf86-video-intel: Update autotools configuration Javier Jardón
2011-02-09 11:49 ` Chris Wilson
2011-02-09 11:58 ` Julien Cristau
2011-02-09 12:02   ` Chris Wilson
2011-02-10 11:02 ` Cyril Brulebois
2011-02-10 16:14   ` Javier Jardón
2011-03-30  1:43   ` Cyril Brulebois
2011-04-02  9:47     ` 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='849307$c9k6e3@azsmga001.ch.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kibi@debian.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