linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: Rolf Eike Beer <eb@emlix.com>
Cc: linux-modules <linux-modules@vger.kernel.org>
Subject: Re: Static build of kmod
Date: Fri, 20 Mar 2020 09:41:18 -0700	[thread overview]
Message-ID: <CAKi4VALBCxct17L9FazuHHfYN_ikim4Pj=Ko3-OY=Odn5pNu+A@mail.gmail.com> (raw)
In-Reply-To: <17444062.evWP73jU2D@devpool35>

On Thu, Mar 19, 2020 at 7:40 AM Rolf Eike Beer <eb@emlix.com> wrote:
>
> Greetings,
>
> since commit b7016153ec87dba2b0f0d182cc8f1e3b12f4dfaf building static kmod is
> disabled. I would like to question that decision.
>
> My use case is as follows: I build a custom BSP and would like to provide
> statically linked host tools. That makes it easy to deploy them at any
> location, and that these tools do not pick up random shared libraries of the
> underlying Linux system when executed. Currently kmod is one of the few
> packages that are not able to build in that way.
>
> I understand that you may want to prevent other tools (e.g. sytemd was
> mentioned in that commit) to link against a static libkmod, and that is fine
> with me. What I would like to get is static kmod tools. For the BSP host tools
> case I don't mind if a libkmod does not exist at all, only the tools are of
> interest.
>
> What do you think?

It's a build system limitation:

./configure -h| grep static
  --enable-static[=PKGS]  build static libraries [default=no]

The --enable-static switch is about building static libraries, and as
a consequence linking the binaries statically.
We don't want libkmod to be built statically because its symbols will
conflict with other libraries
as you mentioned.

If we had a --enable-static-tools switch that made only the tools
static (default false), I think it would be acceptable.

And since you are going to mess with the build system, if you want to
convert kmod to meson it would be very
appreciated :)

thanks
Lucas De Marchi

>
> Regards,
>
> Eike
> --
> Rolf Eike Beer, emlix GmbH, http://www.emlix.com
> Fon +49 551 30664-0, Fax +49 551 30664-11
> Gothaer Platz 3, 37083 Göttingen, Germany
> Sitz der Gesellschaft: Göttingen, Amtsgericht Göttingen HR B 3160
> Geschäftsführung: Heike Jordan, Dr. Uwe Kracke – Ust-IdNr.: DE 205 198 055
>
> emlix - smart embedded open source



-- 
Lucas De Marchi

  reply	other threads:[~2020-03-20 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 14:31 Static build of kmod Rolf Eike Beer
2020-03-20 16:41 ` Lucas De Marchi [this message]
2020-03-23  8:35   ` Rolf Eike Beer

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='CAKi4VALBCxct17L9FazuHHfYN_ikim4Pj=Ko3-OY=Odn5pNu+A@mail.gmail.com' \
    --to=lucas.de.marchi@gmail.com \
    --cc=eb@emlix.com \
    --cc=linux-modules@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).