mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Matthias Klein <matthias.klein@optimeas.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Kernel headers version in OSELAS toolchain & kernel version in the BSP
Date: Tue, 16 Apr 2013 11:58:19 +0200	[thread overview]
Message-ID: <516D20BB.5000108@optimeas.de> (raw)

Hello,

while reading the AppNote "Building Toolchain" I came across the section 
about the naming convention:

The last part (kernel-3.6) defines the kernel header in use for this 
toolchain. This is important, as applications
built with this toolchains must be ran at least on this kernel revision.

That means when I use the toolchain 
arm-cortexa8-linux-gnueabihf_gcc-4.7.3_glibc-2.16.0_binutils-2.22_kernel-3.6-sanitized 
from 2012.12.1
to build a BSP with a 3.4 kernel is wrong? I have done this without any 
problem so far.

What is the recommended approach if I run in such a version conflict?
- Use older toolchains which require a different kernel version?
- Or can I simply adjust / create a new config file for e.g. kernel 3.4 ?

In the ptxconfig file are 2 kernel versions. From the upper toolchain 
example:

PTXCONF_GLIBC_ENABLE_KERNEL="2.6.32"
and
PTXCONF_KERNEL_HEADERS_VERSION="3.6"

What is the difference ?

What speaks against using a very low kernel version for building the 
toolchain ?


Thanks for any tips!

Best regards,

Matthias


-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2013-04-16  9:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16  9:58 Matthias Klein [this message]
2013-04-16 15: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=516D20BB.5000108@optimeas.de \
    --to=matthias.klein@optimeas.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