From: Ian Kumlien <pomac@vapor.com>
To: David Sterba <dsterba@suse.cz>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] [RFC] Add static compile target
Date: Tue, 29 Jan 2013 00:31:53 +0100 [thread overview]
Message-ID: <20130128233153.GI15780@pomac.netswarm.net> (raw)
In-Reply-To: <20130128214651.GH16977@twin.jikos.cz>
On Mon, Jan 28, 2013 at 10:46:51PM +0100, David Sterba wrote:
> Resume: if the distro contains all required libs as static, then your
> patch works.
>
> I wanted to get an idea how the static build would go so my patch
> was a dirty workaroud, that did not work in the end anyway.
To reiterate:
ldd btrfs btrfsck
btrfs:
not a dynamic executable
btrfsck:
not a dynamic executable
du -sh btrfs btrfsck
2,4M btrfs
2,1M btrfsck
strip btrfs
strip btrfsck
du -sh btrfs btrfsck
1,1M btrfs
904K btrfsck
---
And now dynamic:
du -sh btrfs btrfsck
1,5M btrfs
1,3M btrfsck
strip btrfsck ; strip btrfs
du -sh btrfs btrfsck
232K btrfs
156K btrfsck
---
This means that dists are striping binaries...
In which case it would be no problem to have then build the static target,
perhaps we could try to verify if they are available and build btrfs.static
and btrfsck.static if possible....
(I'm using: 64 bit - gcc 4.7.2)
next prev parent reply other threads:[~2013-01-28 23:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 0:09 [PATCH] [RFC] Add static compile target Ian Kumlien
2013-01-27 17:11 ` Gene Czarcinski
2013-01-27 19:22 ` Ian Kumlien
2013-01-28 17:05 ` David Sterba
2013-01-28 18:41 ` Ian Kumlien
2013-01-28 21:46 ` David Sterba
2013-01-28 23:24 ` Ian Kumlien
2013-01-28 23:31 ` Ian Kumlien [this message]
2013-01-29 14:25 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2013-01-26 0:21 [RFC] Add static build target, try two - using git send-email Ian Kumlien
2013-01-26 0:21 ` [PATCH] [RFC] Add static compile target Ian Kumlien
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=20130128233153.GI15780@pomac.netswarm.net \
--to=pomac@vapor.com \
--cc=dsterba@suse.cz \
--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).