From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] kmod: bump version
Date: Wed, 3 Jul 2013 23:49:07 +0200 [thread overview]
Message-ID: <20130703234907.3c4c944e@skate> (raw)
In-Reply-To: <8761wrpbrt.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Wed, 03 Jul 2013 23:35:34 +0200, Peter Korsgaard wrote:
> Thomas> depends !BR2_PREFER_STATIC_LIB
>
> Thomas> in the kconfig dependencies maybe?
>
> We could, yes. I'm fairly sure we have a number of other packages
> that don't handle BR2_PREFER_STATIC_LIB though.
True, but I believe those packages should either be fixed, or marked
as depends on !BR2_PREFER_STATIC_LIB. As we have discussed a number of
times in the past, I believe that a "prefer static libraries" option
doesn't make much sense. Either you /want/ static libraries, or
you /don't/ want static libraries. But a "prefer" option that doesn't
even tell you for which libraries static linking or dynamic linking
will be used is kinda useless. And since kconfig doesn't allow us to
easily provide per-package options to allow the user to define on a
per-library basis whether it should be built static or dynamic, I
believe the only two selections that make sense are: full dynamic or
full static.
Or, as we discussed when talking about building with -fPIC: build
static /and/ dynamic, build dynamic only (default), build static only.
> It will need to be propagated to kmods reverse dependencies (udev,
> network-manager, udisks, ..)
Indeed. I must say I'm somewhat surprised that something relatively
simple like kmod doesn't support static linking.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-07-03 21:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 19:40 [Buildroot] [git commit] kmod: bump version Peter Korsgaard
2013-07-03 21:26 ` Thomas Petazzoni
2013-07-03 21:35 ` Peter Korsgaard
2013-07-03 21:49 ` Thomas Petazzoni [this message]
2013-07-03 21:51 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2014-06-19 15:50 Peter Korsgaard
2014-04-11 18:57 Peter Korsgaard
2014-04-11 22:21 ` Thomas Petazzoni
2014-04-11 22:39 ` Peter Korsgaard
2013-04-12 10:18 Peter Korsgaard
2012-12-15 21:19 Peter Korsgaard
2012-09-13 17:42 Peter Korsgaard
2012-03-22 10:57 Peter Korsgaard
2012-03-08 21:36 Peter Korsgaard
2012-01-19 11:25 Peter Korsgaard
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=20130703234907.3c4c944e@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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