From: Mike Frysinger <vapier@gentoo.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH xfsprogs] libxcmd: link against used libs
Date: Wed, 10 Aug 2016 09:52:36 +0800 [thread overview]
Message-ID: <20160810015236.GD30544@vapier.lan> (raw)
In-Reply-To: <20160809214910.GI19025@dastard>
[-- Attachment #1.1: Type: text/plain, Size: 1020 bytes --]
On 10 Aug 2016 07:49, Dave Chinner wrote:
> On Tue, Aug 09, 2016 at 10:43:43PM +0800, Mike Frysinger wrote:
> > Since this lib uses symbols from libxfs (platform_findsizes) and many
> > symbols from libblkid, link against both. Otherwise, the resulting
> > shared lib has missing symbols which makes linking against annoying.
>
> libxcmd is an internal library, linked directly into the xfsprogs
> binaries. It is never shipped or used outside xfsprogs, so what is
> trying to use libxcmd as a shared library that doesn't also link
> against libblkid or libxfs?
shouldn't internal libs still have coherent linkage ? otherwise you
cause problems even internally for xfs -- any other libs or progs that
link against libxcmd have to list all the libs that libxcmd happen to
use itself. it also means that you get correct link order which is
otherwise not guaranteed. e.g. just because you say libxfs needs to
use libblkid doesn't mean the linker must put that after libxcmd in
the link list.
-mike
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 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:[~2016-08-10 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 14:43 [PATCH xfsprogs] libxcmd: link against used libs Mike Frysinger
2016-08-09 21:49 ` Dave Chinner
2016-08-10 1:52 ` Mike Frysinger [this message]
2016-08-10 2:19 ` 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=20160810015236.GD30544@vapier.lan \
--to=vapier@gentoo.org \
--cc=david@fromorbit.com \
--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