Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Configuring the gpsd package
Date: Tue, 28 Jan 2014 20:42:14 +0100	[thread overview]
Message-ID: <20140128204214.72bfe227@skate> (raw)
In-Reply-To: <20140128190725.GD5596@tarshish>

Dear Baruch Siach,

On Tue, 28 Jan 2014 21:07:25 +0200, Baruch Siach wrote:

> > Correct, but Buildroot checks the selection the user has made in
> > menuconfig against the real configuration of the toolchain, and if they
> > don't match, the Buildroot build doesn't even start. Therefore, there
> > is normally no way to do an incorrect configuration here.
> 
> Interesting. Where is the code implementing this check? Does it detect 
> threading support when the user has not indicated that the toolchain has it 
> (as is apparently the case here)?

It is implemented at
http://git.buildroot.net/buildroot/tree/toolchain/helpers.mk#n246.

And yes, it does both the "positive" check and the "negative" check:

 * If the toolchain has thread support, but the user hasn't selected
   the thread support for his external toolchain, we error out.

 * If the toolchain does not have thread support, but the user has
   selected thread support, we error out.

> > > As to MMU, for some reason this is option is disabled on your 
> > > configuration, although clearly your target has MMU enabled.
> > 
> > Where have you seen Gabi's .config ? I've gone through this thread
> > again, and I haven't seen his .config.
> 
> The message at http://article.gmane.org/gmane.comp.lib.uclibc.buildroot/73739 
> may be interpreted as saying that MMU and HAS_THREADS are not enabled, though 
> it is more likely that only HAS_THREADS is missing.

Ok. We clearly don't have enough informations to help Gabi,
unfortunately.

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

  reply	other threads:[~2014-01-28 19:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01 15:31 [Buildroot] Configuring the gpsd package Gabi Kelemen
2014-01-01 16:20 ` Baruch Siach
2014-01-02  7:53   ` Gabi Kelemen
2014-01-02  8:01     ` Baruch Siach
2014-01-02  8:21       ` Gabi Kelemen
2014-01-02  8:45         ` Baruch Siach
2014-01-02  9:40           ` Gabi Kelemen
2014-01-02 10:04             ` Baruch Siach
2014-01-02 10:29               ` Gabi Kelemen
2014-01-06 15:42                 ` Gabi Kelemen
2014-01-06 15:56                   ` Baruch Siach
2014-01-28 17:33                     ` Thomas Petazzoni
2014-01-28 19:07                       ` Baruch Siach
2014-01-28 19:42                         ` Thomas Petazzoni [this message]
2014-01-29  7:31                           ` Gabi Kelemen
2014-01-29  7:40                             ` Thomas Petazzoni

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=20140128204214.72bfe227@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