public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, paul.chavent@fnac.net
Subject: Re: usage of xfsctrl for embedded development / uuid question
Date: Thu, 14 Jan 2010 19:32:01 -0600	[thread overview]
Message-ID: <4B4FC591.4050104@sandeen.net> (raw)
In-Reply-To: <20100115002938.GC17483@discord.disaster>

Dave Chinner wrote:
> [Please wrap you emails at 72 columns]


>> (3) regeneration of configure
>>
>>     The regeneration of configure fails whith this message
>>
>>     # rm configure
>>     # make configure
>>     [...]
>>     autoconf
>>     configure.in:101: error: possibly undefined macro: AC_HAVE_BLKID_TOPO
>>       If this token and others are legitimate, please use m4_pattern_allow.
>>       See the Autoconf documentation.
> 
> 'make distclean' is the correct way to remove the configuration and
> rebuild it. That should make the problem go away.

This is also a bug thanks to yours truly in the latest release,
Christoph sent a patch to fix it:

[PATCH] xfsprogs: add package_blkid.m4 to the distributed files

-Eric
 
> Cheers,
> 
> Dave.

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

  reply	other threads:[~2010-01-15  1:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17182907.184441263481368019.JavaMail.www@wsfrf1112>
2010-01-15  0:29 ` usage of xfsctrl for embedded development / uuid question Dave Chinner
2010-01-15  1:32   ` Eric Sandeen [this message]
     [not found] <5340782.170001263558076439.JavaMail.www@wsfrf1111>
2010-01-15 12:46 ` Dave Chinner
2010-01-15 21:11   ` Paul Chavent
2010-01-17 11:46     ` 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=4B4FC591.4050104@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=david@fromorbit.com \
    --cc=paul.chavent@fnac.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