mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Hänel-Baas, Alexander" <alexander.haenel-baas@sieb-meyer.de>
To: "Jürgen Borleis" <jbe@pengutronix.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Kernel CONFIG_LOCALVERSION
Date: Mon, 8 Jun 2015 08:47:33 +0000	[thread overview]
Message-ID: <9BA84827B30CBE4996725F98F7DC912365009205@SMExchange01.siebmeyer.org> (raw)
In-Reply-To: <201506081037.43072.jbe@pengutronix.de>

> You could scan (by sourcing) the file

> ${PTXDIST_PLATFORMCONFIGDIR}/${PTXCONF_KERNEL_CONFIG}

Yes, actually I do that.
I hope we get: $ ptxdist print PTXCONF_KERNEL_LOCALVERSION in the future.

Regards
Alexander


-----Ursprüngliche Nachricht-----
Von: Jürgen Borleis [mailto:jbe@pengutronix.de] 
Gesendet: Montag, 8. Juni 2015 10:38
An: Hänel-Baas, Alexander
Cc: ptxdist@pengutronix.de
Betreff: Re: AW: [ptxdist] Kernel CONFIG_LOCALVERSION

Hi Alexander,

On Monday 08 June 2015 10:25:12 Hänel-Baas, Alexander wrote:
> > What does "localversion" mean in your context?
>
> I mean the kernel CONFIG_LOCALVERSION in the kernel .config file. I 
> can set this localversion in ptxdist menuconfig kernel -> general 
> setup <- Local version.
>
> Normally this string was append to kernel version.
>
> Your suggest is right but I miss the local version append.
>
> Look here:
> $ ptxdist print PTXCONF_KERNEL_VERSION
> give: 3.14.17
>
> But in the kernel .config file stands:
> #
> # General setup
> #
> CONFIG_INIT_ENV_ARG_LIMIT=32
> CONFIG_CROSS_COMPILE=""
> CONFIG_COMPILE_TEST=y
> CONFIG_LOCALVERSION="alex"                 <- here!!!
> # CONFIG_LOCALVERSION_AUTO is not set
>
> So I should have get: 3.14.17-alex.
>
> There is no problem with ptxdist, always works fine.
> Only i need access to this CONFIG_LOCALVERSION string in my own rules 
> file because we build different packages depend on the Locale version 
> from the Kernel.

You could scan (by sourcing) the file

 ${PTXDIST_PLATFORMCONFIGDIR}/${PTXCONF_KERNEL_CONFIG}

because this file is managed by PTXdist and it will be copied to your kernel prior building it (and so ends up as ".config" in the kernel's source tree).

Regards,
Juergen

--
Pengutronix e.K.                              | Juergen Borleis             | Industrial Linux Solutions                    | http://www.pengutronix.de/  |
-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-06-08  8:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08  7:30 Hänel-Baas, Alexander
2015-06-08  7:57 ` Jürgen Borleis
2015-06-08  8:25   ` Hänel-Baas, Alexander
2015-06-08  8:37     ` Jürgen Borleis
2015-06-08  8:47       ` Hänel-Baas, Alexander [this message]
2015-06-08  9:05     ` Michael Olbrich

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=9BA84827B30CBE4996725F98F7DC912365009205@SMExchange01.siebmeyer.org \
    --to=alexander.haenel-baas@sieb-meyer.de \
    --cc=jbe@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