Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Vincent McIntyre <vincent.mcintyre@csiro.au>
Cc: linux-xfs@vger.kernel.org
Subject: Re: xfsprogs-dev failing to build
Date: Mon, 23 Jul 2018 23:22:00 -0700	[thread overview]
Message-ID: <20180724062200.GT4813@magnolia> (raw)
In-Reply-To: <20180724043734.GI27624@mayhem.atnf.CSIRO.AU>

On Tue, Jul 24, 2018 at 02:37:34PM +1000, Vincent McIntyre wrote:
> On Mon, Jul 23, 2018 at 09:27:38PM -0700, Darrick J. Wong wrote:
> > On Tue, Jul 24, 2018 at 02:09:44PM +1000, Vincent McIntyre wrote:
> > > Hi
> > > 
> > > I am trying to build the latest xfsprogs on an older system,
> > > details below. The configure script is failing on what appears
> > > to be an unexpanded m4 macro,
> > > 
> > >   PKG_CHECK_MODULES(libicu, icu-i18n, have_libicu=yes, have_libicu=no)
> > 
> > Hmmm, I thought that pkg.m4 would be pulled in via aclocal
> > automatically, but I could be wrong. :/
> > 
> > What version of pkg-config (or I guess pkgconf?) is on the system?
> > 
> 
> It was not actually installed, and that was the problem.
> The tree builds ok now, and xfs_repair -n works ok.
> 
> A bit odd pkg-config was not installed, I had installed the
> 'build-essential' metapackage but I guess it didn't pull in.
> 
> > > I'm not quite sure how to work around this or if it is a bug.
> > > Any advice would be appreciated.
> > 
> > Definitely some sort of bug...
> 
> I think the only fix needed is for the xfs.org faq page
> 
> - apt-get install libtool automake gettext libblkid-dev uuid-dev
> + apt-get install libtool automake gettext libblkid-dev uuid-dev pkg-config
> 
> Possibly libicu-dev should be added to the list also.

FWIW they're both listed in debian/control as build dependencies...

Does anyone out there have the connections to the xfs.org maintainers to
fix that...?

--D

> 
> Thanks for the fast response.
> Cheers
> Vince
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-07-24  7:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24  4:09 xfsprogs-dev failing to build Vincent McIntyre
2018-07-24  4:27 ` Darrick J. Wong
2018-07-24  4:37   ` Vincent McIntyre
2018-07-24  6:22     ` Darrick J. Wong [this message]
2018-07-24  6:32       ` Eric Sandeen

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=20180724062200.GT4813@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=vincent.mcintyre@csiro.au \
    /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