From: Andreas Gruenbacher <agruen@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric Sandeen <sandeen@sandeen.net>,
Mike Frysinger <vapier@gentoo.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [patch] fix parallel build failures in xfsprogs-3.0.0
Date: Sun, 8 Mar 2009 14:09:28 +0100 [thread overview]
Message-ID: <200903081409.28808.agruen@suse.de> (raw)
In-Reply-To: <20090304172727.GA21463@infradead.org>
On Wednesday, 4 March 2009 18:27:27 Christoph Hellwig wrote:
> I've tried to port the patch you checked into xfsprogs (see below for
> the diff), but it fails to build for me. Any idea what might have
> gone wrong?
git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git is missing the following
commit from ssh://master.kernel.org/pub/scm/linux/kernel/git/agruen/acl.git:
commit 8de7788c29d2656f8d52d98327a80e4dfd1e3898
Author: Barry Naujok <bnaujok@sgi.com>
Date: Tue Jan 23 14:51:14 2007 +0000
Fix cross-compile issues with libtool and compiler.
This is equivalent to commit de7b3f6 from Barry Naujok <bnaujok@sgi.com>
in the acl package, and part of the Gentoo package, as pointed out by
Mike Frysinger <vapier@gentoo.org>.
Signed-off-by: Andreas Gruenbacher <agruen@suse.de>
While looking into this, I noticed that the attr and acl packages were calling
AC_PROG_LIBTOOL both in configure.in and m4/package_utilies.m4. I have
removed the redundant call from m4/package_utilies.m4 now.
Andreas
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-03-08 13:11 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 5:10 [patch] fix parallel build failures in xfsprogs-3.0.0 Mike Frysinger
2009-02-24 5:20 ` Eric Sandeen
2009-02-24 5:22 ` Eric Sandeen
2009-02-24 7:21 ` Mike Frysinger
2009-02-24 13:15 ` Christoph Hellwig
2009-02-24 14:53 ` Mike Frysinger
2009-02-24 15:14 ` Felix Blyakher
2009-02-24 15:37 ` Mike Frysinger
2009-02-24 18:46 ` Christoph Hellwig
2009-02-24 22:22 ` Andreas Gruenbacher
2009-02-24 23:45 ` Mike Frysinger
2009-02-26 0:26 ` Andreas Gruenbacher
2009-02-26 1:03 ` Mike Frysinger
2009-02-26 12:23 ` Andreas Gruenbacher
2009-02-26 15:17 ` Mike Frysinger
2009-02-26 17:17 ` Andreas Gruenbacher
2009-02-26 18:08 ` Mike Frysinger
2009-02-27 7:22 ` Greg Banks
2009-02-27 9:55 ` Andreas Gruenbacher
2009-03-01 1:31 ` Greg Banks
2009-03-01 7:58 ` Mike Frysinger
2009-03-03 15:53 ` Christoph Hellwig
2009-02-27 17:35 ` Andreas Gruenbacher
2009-03-04 17:27 ` Christoph Hellwig
2009-03-08 13:09 ` Andreas Gruenbacher [this message]
2009-03-10 16:41 ` Andreas Gruenbacher
2009-03-16 7:05 ` Christoph Hellwig
2009-03-16 7:31 ` Mike Frysinger
2009-03-16 9:53 ` Andreas Gruenbacher
2009-03-16 21:02 ` Christoph Hellwig
2009-03-24 13:12 ` Christoph Hellwig
2009-03-24 18:18 ` Andreas Gruenbacher
2009-03-25 19:03 ` Christoph Hellwig
2009-03-16 6:51 ` Christoph Hellwig
2009-03-27 16:02 ` Christoph Hellwig
2009-03-27 16:30 ` Mike Frysinger
2009-03-27 18:31 ` Christoph Hellwig
2009-02-26 23:03 ` Christoph Hellwig
2009-02-28 0:07 ` Andreas Gruenbacher
2009-02-28 22:27 ` Eric Sandeen
2009-03-01 1:41 ` Greg Banks
2009-03-01 17:23 ` Andreas Gruenbacher
2009-03-03 15:55 ` Christoph Hellwig
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=200903081409.28808.agruen@suse.de \
--to=agruen@suse.de \
--cc=hch@infradead.org \
--cc=sandeen@sandeen.net \
--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 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.