linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 5.10
Date: Thu, 21 Jan 2021 16:37:59 +0100	[thread overview]
Message-ID: <20210121153759.GZ6430@twin.jikos.cz> (raw)
In-Reply-To: <20210118222021.11603-1-dsterba@suse.com>

On Mon, Jan 18, 2021 at 11:20:21PM +0100, David Sterba wrote:
> Hi,
> 
> btrfs-progs version 5.10 have been released.

I got a report that static build is broken. It's caused by libmount that
has some internal functions with the same name as is in progs
(canonicalize_path, parse_size). I don't have a final fix, only
workarounds hiding or renaming the functions but there are still some
other problems that can't be solved by that.

ld: /../lib64/libmount.a(libcommon_la-canonicalize.o): in function `canonicalize_dm_name':
util-linux-2.34/lib/canonicalize.c:58: multiple definition of `canonicalize_dm_name';
	common/path-utils.static.o:btrfs-progs/common/path-utils.c:286: first defined here

similar for canonicalize_path and parse_size, and then it's

ld: ../lib64/libmount.a(la-utils.o): in function `mnt_get_gid':
util-linux-2.34/libmount/src/utils.c:625: warning: Using 'getgrnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
ld: ../lib64/libmount.a(la-utils.o): in function `mnt_get_uid':
util-linux-2.34/libmount/src/utils.c:598: warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
ld: ../lib64/libmount.a(la-utils.o): in function `mnt_get_username':
util-linux-2.34/libmount/src/utils.c:577: warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

Only warnings but I haven't checked if that affects runtime.

ld: ../lib64/libmount.a(la-optstr.o): in function `mnt_optstr_fix_secontext':
util-linux-2.34/libmount/src/optstr.c:909: undefined reference to `selinux_trans_to_raw_context'
ld: util-linux-2.34/libmount/src/optstr.c:934: undefined reference to `freecon'

The functions are from selinux that's pulled by libmount.so.1 and adds
yet another library dependency.

We want to support the static build so this will get fixed.

  reply	other threads:[~2021-01-21 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 22:20 Btrfs progs release 5.10 David Sterba
2021-01-21 15:37 ` David Sterba [this message]
2021-02-16 11:48 ` Filipe Manana

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=20210121153759.GZ6430@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).