public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Christoph Hellwig <hch@infradead.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfs-cmds: fix parallel installs in include/ dirs
Date: Tue, 30 Dec 2008 14:23:45 -0600	[thread overview]
Message-ID: <495A8351.3010604@sandeen.net> (raw)
In-Reply-To: <200812301519.42689.vapier@gentoo.org>

Mike Frysinger wrote:
> On Tuesday 30 December 2008 12:18:25 Christoph Hellwig wrote:
>> On Tue, Dec 30, 2008 at 09:07:30AM -0500, Mike Frysinger wrote:
>>> acl-2.2.47 built fine for me with `./configure && make` and this patch
>>> ...
>> Works now after a make distclean for me.
>>
>>> that said, if the only purpose of this is to make sure there are symlinks
>>> in include/, why not do it at the tail end of configure ?  then there
>>> will be no weird parallel magic to worry about, and everything will
>>> always be available once configure has finished.
>> I'll leave that to Eric or anyone else who wants to play a build system
>> expert on TV :)
> 
> it's easy to do, i just dont know how people feel about the idea in general

Doesn't much matter to me; not sure what is customary.  Both ways work
fine, I think.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2008-12-30 20:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 22:19 [PATCH] xfs-cmds: fix parallel installs in include/ dirs Eric Sandeen
2008-12-30 11:52 ` Christoph Hellwig
2008-12-30 12:49   ` Christoph Hellwig
2008-12-30 14:07     ` Mike Frysinger
2008-12-30 17:18       ` Christoph Hellwig
2008-12-30 20:19         ` Mike Frysinger
2008-12-30 20:23           ` Eric Sandeen [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=495A8351.3010604@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hch@infradead.org \
    --cc=vapier@gentoo.org \
    --cc=xfs@oss.sgi.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