All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Depending on uClibc configuration variables
Date: Wed, 13 Jul 2011 16:26:22 +0200	[thread overview]
Message-ID: <CACTFLAO+rT2UEZ+wJ_8ePQwbbG6m9B4SfPtm8chUzkzS_PoKGw@mail.gmail.com> (raw)
In-Reply-To: <87mxgifyd1.fsf@macbook.be.48ers.dk>

On Wed, Jul 13, 2011 at 9:12 AM, Peter Korsgaard <jacmet@uclibc.org> wrote:
>>>>>> "Daniel" == Daniel Mack <zonque@gmail.com> writes:
>
> ?Daniel> Is there a clever way to depend on variables set in the uClibc
> ?Daniel> configuration directly in package Config.in files? Something like
> ?Daniel> UCLIBC_HAS_EPOLL for example?
>
> Unfortunately not. We have tweaked the default uClibc config so that all
> packages should build (or patched packages where needed), so it normally
> shouldn't be needed.
>
> I consider using a custom uClibc configuration an advanced feature,
> where the user is supposed to know what they are doing (tm).

The thing is that I have been teaching new DNS lookup functions to
libuClibc which will be built depending on a new config variable
switch. The puropose for this is to make connman build in buildroot,
and I have it running here already. However, to prevent breakage, I
would like to depend on this new uClibc configuration directive, so
people can't select the new package unless they have a recent uClibc
with this new option selected. How would I do this?


Thanks,
Daniel

  reply	other threads:[~2011-07-13 14:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 23:05 [Buildroot] Depending on uClibc configuration variables Daniel Mack
2011-07-13  7:12 ` Peter Korsgaard
2011-07-13 14:26   ` Daniel Mack [this message]
2011-07-13 14:31     ` Thomas Petazzoni
2011-07-13 14:36       ` Daniel Mack
2011-07-13 16:24         ` Thomas Petazzoni
2011-07-13 16:31           ` Peter Korsgaard
2011-07-13 16:36             ` Daniel Mack
2011-07-13 17:15               ` Peter Korsgaard

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=CACTFLAO+rT2UEZ+wJ_8ePQwbbG6m9B4SfPtm8chUzkzS_PoKGw@mail.gmail.com \
    --to=zonque@gmail.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.