public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [patch] fix parallel build failures in xfsprogs-3.0.0
Date: Thu, 26 Feb 2009 10:17:28 -0500	[thread overview]
Message-ID: <200902261017.30017.vapier@gentoo.org> (raw)
In-Reply-To: <200902261323.09312.agruen@suse.de>

On Thursday 26 February 2009 07:23:08 Andreas Gruenbacher wrote:
> On Thursday 26 February 2009 02:03:29 Mike Frysinger wrote:
> > On Wednesday 25 February 2009 19:26:14 Andreas Gruenbacher wrote:
> > > On Wednesday, 25 February 2009 0:45:25 Mike Frysinger wrote:
> > > > and for attr.git:
> > > > http://sources.gentoo.org/sys-apps/attr/files/attr-2.4.39-gettext.pat
> > > >ch
> > >
> > > This functionality already exists (in both the acl and attr packages).
> >
> > was this in the last release (2.4.43) ?  either way, can you highlight
> > the code you're referring to so there's no confusion on my part ;)
>
> Hmm ... so there code that this patch adds to include/gettext.h already
> exists in include/config.h.in, but ENABLE_GETTEXT isn't being defined
> anywhere. So this part of your patch still seems to be needed, in both the
> attr and acl packages.
>
> When I add it, I get this far:
>
> 	$ make aclocal.m4
> 	$ autoconf
> 	configure:3493: error: possibly undefined macro: AC_PROG_LIBTOOL
>       If this token and others are legitimate, please use m4_pattern_allow.
>       See the Autoconf documentation.
>
> It turns out that aclocal.m4 is created with only the macros in the m4/
> directory, and AC_PROG_LIBTOOL is not among them; this can be checked with:
>
> 	$ aclocal --acdir=m4 --verbose
>
> This would usually be fixed by including the macros in m4/ in addition, but
> then I run into the next problem:
>
> 	$ aclocal -I m4
> 	$ autoconf
> 	[...]
> 	configure: error: cannot run /bin/sh ./config.sub
>
> As per one of the libtool info pages,
>
> > In order to use libtool, you need to include the following files with
> > your package:
> >
> > `config.guess'
> >      Attempt to guess a canonical system name.
> >
> > `config.sub'
> >      Canonical system name validation subroutine script.
> >
> > `install-sh'
> >      BSD-compatible `install' replacement script.
> >
> > `ltmain.sh'
> >      A generic script implementing basic libtool functionality.
>
> after adding config.guess, config.sub from automake, and ltmain.sh from
> libtool (we already have our own install-sh), the package builds again.
>
> I'm attaching a diff relative to the current repo excluding config.guess,
> config.sub, and ltmain.sh which should be on your systems from automake and
> libtool already.
>
> This is quite insane. Is there a more reasonable way?

yes.  i dont know why the xfs progs have been packaging these autogenerated 
files by themselves.

- remove aclocal.m4 from git
- run `aclocal -I m4`
- run `libtoolize -c -f`
- run `autoconf`
- copy the remaining files libtool wanted (normally created by automake, but 
acl isnt using automake, so we cant use it to copy the files for us)
-mike

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

  reply	other threads:[~2009-02-26 15:18 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 [this message]
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
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=200902261017.30017.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=agruen@suse.de \
    --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