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:24:39 +0100 [thread overview]
Message-ID: <20130128232439.GH15780@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:
> On Mon, Jan 28, 2013 at 07:41:01PM +0100, Ian Kumlien wrote:
> > > I tried to build 'btrfs' only and moved the static libs definition to
> > > the beginning (still needs the uuid static library though):
> >
> > Which you haven't included - you sould also include btrfsck at bare
> > minimum ;)
> >
> > > --- a/Makefile
> > > +++ b/Makefile
> > > @@ -19,6 +19,7 @@ prefix ?= /usr/local
> > > +STATIC_LIBS= -lpthread
> > > +static: CFLAGS += -static
> > > +static: LIBS = $(STATIC_LIBS)
> >
> > I think you mean += since this will not build since it misses libuuid
> >
> > If you don't have the libs to do a static build - that is one thing but
> > it should work =)
>
> Resume: if the distro contains all required libs as static, then your
> patch works.
Yeah... But if it's shipped in a dist i assume they will create static
versions and srip them, just like it seems that other dists does.
> 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.
=) I was a bit confused about it - but you are right, 'btrfs' and
'btrfsck' is the only two we really need to have as static...
> david
next prev parent reply other threads:[~2013-01-28 23:24 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 [this message]
2013-01-28 23:31 ` Ian Kumlien
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=20130128232439.GH15780@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).