From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@kernel.org
Subject: [Bug 201287] New: xfsprogs 4.17 and later can't be built as static binaries anymore
Date: Sat, 29 Sep 2018 23:03:12 +0000 [thread overview]
Message-ID: <bug-201287-201763@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=201287
Bug ID: 201287
Summary: xfsprogs 4.17 and later can't be built as static
binaries anymore
Product: File System
Version: 2.5
Kernel Version: n/a
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: XFS
Assignee: filesystem_xfs@kernel-bugs.kernel.org
Reporter: dilfridge@gentoo.org
Regression: No
In Gentoo we offer the possibility to build xfsprogs fully static, e.g. for
initramdisks.
This still worked fine with 4.14.
With 4.17 and 4.18 we however get:
../libfrog/.libs/libfrog.a(convert.o): In function `gid_from_string':
convert.c:(.text+0x984): warning: Using 'getgrnam' in statically linked
applications requires at runtime the shared libraries from the glibc version
used for linking
and final linking fails.
See also https://bugs.gentoo.org/666196
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2018-09-30 5:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 23:03 bugzilla-daemon [this message]
2018-09-30 0:06 ` [Bug 201287] xfsprogs 4.17 and later can't be built as static binaries anymore bugzilla-daemon
2018-09-30 0:18 ` bugzilla-daemon
2018-09-30 0:26 ` bugzilla-daemon
2018-09-30 0:28 ` bugzilla-daemon
2018-09-30 0:32 ` bugzilla-daemon
2018-09-30 3:00 ` bugzilla-daemon
2018-09-30 4:59 ` bugzilla-daemon
2018-09-30 5:18 ` bugzilla-daemon
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=bug-201287-201763@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@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).