All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/zeromq: enable kernel-based feature flags
Date: Tue, 21 Apr 2015 22:47:51 +0200	[thread overview]
Message-ID: <20150421224751.1eebfde3@free-electrons.com> (raw)
In-Reply-To: <5509FBEB.8040505@mind.be>

Dear Arnout Vandecappelle,

On Wed, 18 Mar 2015 23:27:55 +0100, Arnout Vandecappelle wrote:

>  It's been a while ago, of course, but I think one problem was that the symbols
> are also defined by the toolchain, so they exist even if the kernel doesn't
> support them.

If the flags exist in the toolchain, then it means that the toolchain
is using a certain version of the kernel headers. Running with a kernel
older than that will anyway not work.

I mean, there are zillions of configure script that tests if the
toolchain has syscall foo() or bar() by simply doing a compile time
test. They don't actually check if the user is stupid enough to run on
a system that has a kernel older than the kernel headers + C library
combination used in the toolchain.

Or am I missing something specific to those flags?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-04-21 20:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06  9:25 [Buildroot] [PATCH 1/1] package/zeromq: enable kernel-based feature flags Lionel Orry
2015-03-15 22:28 ` Thomas Petazzoni
2015-03-16  6:43   ` Lionel Orry
2015-03-16  8:05     ` Thomas Petazzoni
2015-03-18 22:27     ` Arnout Vandecappelle
2015-04-21 20:47       ` Thomas Petazzoni [this message]
2015-04-21 21:48         ` Arnout Vandecappelle
  -- strict thread matches above, loose matches on Subject: below --
2015-04-21 13:30 Lionel Orry
2015-04-21 13:33 ` Thomas Petazzoni
2015-04-21 13:39   ` Lionel Orry
2015-04-21 20:19     ` Arnout Vandecappelle
2015-04-22  6:01       ` Lionel Orry
2015-04-22  7:38         ` Thomas Petazzoni
2015-04-22  5:54     ` Lionel Orry

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=20150421224751.1eebfde3@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.