From: Sergei Trofimovich <slyich@gmail.com>
To: Ian Kumlien <pomac@vapor.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: add static compile target
Date: Sat, 9 Feb 2013 22:48:51 +0300 [thread overview]
Message-ID: <20130209224851.4560edf9@sf> (raw)
In-Reply-To: <20130209185144.GQ15780@pomac.netswarm.net>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
On Sat, 9 Feb 2013 19:51:44 +0100
Ian Kumlien <pomac@vapor.com> wrote:
> On Sat, Feb 09, 2013 at 08:57:42PM +0300, Sergei Trofimovich wrote:
> > On Sat, 9 Feb 2013 00:19:29 +0100
> > Ian Kumlien <pomac@demius.net> wrote:
> >
> > > Sometimes, when you least expect it, a static binary is what you need to
> > > rescue your data... Or just get a good enough handle on things to make
> > > it work again ;)
> > >
> > > "make static" is a gift to you, dear user with filesystem problems!
> >
> > What's wrong with conventional LDFLAGS=-static make?
>
> That doesn't work for me, does it actually work for you?
>
> I'd say it wouldn't without adding LDFLAGS so that the compiler gets it
> for all object compilations.
-static is link-only flag.
Mostly yes, it works.
LDFLAGS="-static -pthread" make
make all binaries static.
It needs
sys-apps/util-linux
sys-libs/e2fsprogs-libs
sys-fs/e2fsprogs
sys-libs/zlib
to be built with USE=static-libs .
$ ldd btrfs
not a dynamic executable
$ ldd mkfs.btrfs
not a dynamic executable
None of built binaries is dynamic.
--
Sergei
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-02-09 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 23:19 [PATCH] Btrfs-progs: add static compile target Ian Kumlien
2013-02-09 17:57 ` Sergei Trofimovich
2013-02-09 18:51 ` Ian Kumlien
2013-02-09 19:48 ` Sergei Trofimovich [this message]
2013-02-09 22:21 ` Ian Kumlien
2013-02-12 13:55 ` David Sterba
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=20130209224851.4560edf9@sf \
--to=slyich@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pomac@vapor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.