public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: fdmanana@kernel.org, fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] Fix error message when xfs handle library not found
Date: Wed, 13 Feb 2019 08:15:26 +1100	[thread overview]
Message-ID: <20190212211526.GK20493@dastard> (raw)
In-Reply-To: <93a04478-db84-95f2-9957-5588dc0a54ed@sandeen.net>

[cc linux-xfs@vger.kernel.org]

On Tue, Feb 12, 2019 at 12:59:02PM -0600, Eric Sandeen wrote:
> On 2/12/19 12:18 PM, fdmanana@kernel.org wrote:
> > From: Filipe Manana <fdmanana@suse.com>
> > 
> > The error message mentions a "make install-lib" target from xfsprogs,
> > however that target does not exists in xfsprogs, what exists is a
> > target named "install-dev". So fix that and replace "install-lib" with
> > "install-dev".
> > 
> > Signed-off-by: Filipe Manana <fdmanana@suse.com>
> > ---
> >  m4/package_xfslibs.m4 | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/m4/package_xfslibs.m4 b/m4/package_xfslibs.m4
> > index 9be56e11..ad019518 100644
> > --- a/m4/package_xfslibs.m4
> > +++ b/m4/package_xfslibs.m4
> > @@ -83,7 +83,7 @@ AC_DEFUN([AC_PACKAGE_NEED_ATTRLIST_LIBHANDLE],
> >          echo
> >          echo 'FATAL ERROR: could not find a current XFS handle library.'
> >          echo 'Install or upgrade the XFS library package.'
> 
> To fix things up a bit more, I'd probably not refer to the "XFS library package"
> because I'm not sure that exists anywhere either, does it?
> 
> In fedora/rhel land, it's in xfsprogs & xfsprogs-devel for development.
> 
> Not sure about suse or debian or ...?

Debian:

$ apt-file search libhandle
....
xfslibs-dev: /lib/libhandle.a
xfslibs-dev: /lib/libhandle.so
xfslibs-dev: /usr/lib/libhandle.a
xfslibs-dev: /usr/lib/libhandle.la
xfsprogs: /lib/libhandle.so.1
xfsprogs: /lib/libhandle.so.1.0.3
$

So the libhandle library DSO is shipped in xfsprogs. The /static/
library is shipped in xfslibs-dev.

So what is fstests requiring here - the DSO or the static library?
If it's the static library, then why does it need that and why can't
it use the DSO shipped as part of the main xfsprogs package?

> Not a huge deal but if nobody ships xfsprogs-libs (or similar) then maybe best
> to fix that line as well.
> 
> > -        echo 'Alternatively, run "make install-lib" from the xfsprogs source.'
> > +        echo 'Alternatively, run "make install-dev" from the xfsprogs source.'
> 
> and yeah, this part makes sense.

Only if it requires the static libhandle.a library.

But that said, we should probably get rid of the static library and
just ship the DSO - I can't think of a good reason for shipping a
static version of a DSO in a "dev" package these days.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2019-02-12 21:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 18:18 [PATCH] Fix error message when xfs handle library not found fdmanana
2019-02-12 18:59 ` Eric Sandeen
2019-02-12 21:15   ` Dave Chinner [this message]
2019-02-12 23:46     ` Eric Sandeen
2019-02-13  2:18       ` Dave Chinner

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=20190212211526.GK20493@dastard \
    --to=david@fromorbit.com \
    --cc=fdmanana@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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