From: Mike Frysinger <vapier@gentoo.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs-oss <xfs@oss.sgi.com>, Eric Sandeen <sandeen@sandeen.net>
Subject: Re: [patch] fix parallel build failures in xfsprogs-3.0.0
Date: Mon, 16 Mar 2009 03:31:48 -0400 [thread overview]
Message-ID: <200903160331.53142.vapier@gentoo.org> (raw)
In-Reply-To: <20090316070550.GA628@infradead.org>
[-- Attachment #1.1: Type: text/plain, Size: 807 bytes --]
On Monday 16 March 2009 03:05:50 Christoph Hellwig wrote:
> On Tue, Mar 10, 2009 at 05:41:06PM +0100, Andreas Gruenbacher wrote:
> > As it turns out, I was running into more trouble with libtoolize from
> > libtool 2.2.6. See this commit in attr.git:
> >
> > commit 604290f79a199eb0c73a0cd05a473e1801a00673
> > Author: Andreas Gruenbacher <agruen@suse.de>
> > Date: Tue Mar 10 17:00:35 2009 +0100
> >
> > More libtoolize fixes
>
> That patch breaks the commit for me:
>
> hch@brick:~/work/attr$ make
> libtoolize -c -i -f
> libtoolize: unrecognized option `-i'
> Try `libtoolize --help' for more information.
> make: *** [include/builddefs] Error 1
-i is new to libtool-2
usually what i do is something like:
args=
libtoolize -n --install 2>/dev/null && args="-i"
libtoolize -c -f $args
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-03-16 7:32 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
2009-03-10 16:41 ` Andreas Gruenbacher
2009-03-16 7:05 ` Christoph Hellwig
2009-03-16 7:31 ` Mike Frysinger [this message]
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=200903160331.53142.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=hch@infradead.org \
--cc=sandeen@sandeen.net \
--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