From: Florian Westphal <fw@strlen.de>
To: Justin Swartz <justin.swartz@risingedge.co.za>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, rkolchmeyer@google.com,
pablo@netfilter.org
Subject: Re: [PATCH resend] ebtables: extend the 'static' build target fix.
Date: Thu, 28 Jul 2022 12:37:07 +0200 [thread overview]
Message-ID: <20220728103707.GB4816@breakpoint.cc> (raw)
In-Reply-To: <e8710ee1bd03701352fb89dfcc385308@risingedge.co.za>
Justin Swartz <justin.swartz@risingedge.co.za> wrote:
> > So, as far as I can see, "make static" does the same thing it
> > did prio to automake/libtool conversion, place all the extensions
> > and libebtables in the "static" binary, but link libc.so dynamically.
>
> Thanks for the clarification.
>
> I assumed "make static" was intended to produce an actual static binary.
>
> As part of a small distribution that I use on a few bridging firewalls,
> I have only ebtables and busybox, both built as static binaries, plus
> inittab and a few init scripts.
>
> I don't mind patching "Makefile.am" for myself, but I would also be happy
> to submit something like the following, if nice-to-have, to provide an
> "allstatic" which shouldn't break anything for those who require "static"
> in its current form.
If you can't get what you need without patching the ebables build
scripts then sure, feel free to submit a change that allows to build a
fully static binary.
prev parent reply other threads:[~2022-07-28 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 8:14 [PATCH] ebtables: extend the 'static' build target fix Justin Swartz
2022-07-03 9:52 ` [PATCH resend] " Justin Swartz
2022-07-28 8:13 ` Florian Westphal
2022-07-28 8:56 ` Justin Swartz
2022-07-28 10:37 ` Florian Westphal [this message]
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=20220728103707.GB4816@breakpoint.cc \
--to=fw@strlen.de \
--cc=justin.swartz@risingedge.co.za \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=rkolchmeyer@google.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.