mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Forcing kernel options from userspace package
Date: Mon, 26 Jun 2017 10:40:08 +0200	[thread overview]
Message-ID: <20170626084008.r2dwyuqqoijc6fgc@pengutronix.de> (raw)
In-Reply-To: <00A83466-B656-412F-BFF6-600C7A38BE19@ruediger.engineering>

Hi,

On Tue, Jun 06, 2017 at 07:06:47PM +0000, christoph@ruediger.engineering wrote:
> is there a way to force a specific kernel option by selecting a userland package?
> 
> The concrete case:
> I’m working on a project that uses the SCTP protocol for which I’ve created a
> libsctp package for the userland support library of SCTP. The libsctp package
> is forced by my application via the corresponding “select LIBSCTP” in
> rules/my_app.in. Now I’m looking for a way to have libsctp force the kernel’s
> config flag CONFIG_IP_SCTP to be set. Does ptxdist provide any such mechanism
> or are the userland’s KConfig and the kernel’s KConfig totally separated?

That's not possible and unlikely to change. That would mean calling kconfig
for the kernel in 'ptxdist menuconfig' and that's not possible. The kernel
source code may not be available at that point.
I suggest a validation script that checks, that the two configs fit
together. Parsing ptxconfig is quite simple.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-06-26  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 19:06 christoph
2017-06-26  8:40 ` Michael Olbrich [this message]
2017-06-27  8:29   ` Alexander Dahl

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=20170626084008.r2dwyuqqoijc6fgc@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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