From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@kernel.org
Subject: [Bug 201287] xfsprogs 4.17 and later can't be built as static binaries anymore
Date: Sun, 30 Sep 2018 00:06:26 +0000 [thread overview]
Message-ID: <bug-201287-201763-52jfFh2E34@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201287-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201287
Eric Sandeen (sandeen@sandeen.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@sandeen.net
--- Comment #1 from Eric Sandeen (sandeen@sandeen.net) ---
Is there a recipe to demonstrate this failure in the upstream git tree w/o the
gentoo patches or build environment?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-09-30 6:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 23:03 [Bug 201287] New: xfsprogs 4.17 and later can't be built as static binaries anymore bugzilla-daemon
2018-09-30 0:06 ` bugzilla-daemon [this message]
2018-09-30 0:18 ` [Bug 201287] " 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-52jfFh2E34@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).