From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mongrel2: Needs a glibc or a uClibc-0.9.34-git based toolchain
Date: Wed, 22 May 2013 16:43:32 +0200 [thread overview]
Message-ID: <20130522164332.3a293c0d@skate> (raw)
In-Reply-To: <1369231808-11185-1-git-send-email-markos.chandras@gmail.com>
Dear Markos Chandras,
On Wed, 22 May 2013 15:10:08 +0100, Markos Chandras wrote:
> + # {get,make,swap}context functions present in
> + # glibc and in uClibc's master branch.
> + depends on BR2_UCLIBC_VERSION_SNAPSHOT || !BR2_TOOLCHAIN_BUILDROOT
> help
> Mongrel2 is an application, language, and network architecture
> agnostic web server that focuses on web applications using
An external toolchain can be uClibc based... but we don't know which
version. However, since no uClibc stable release has been released with
this feature, I don't expect any external toolchain today to have this
feature enabled. So something like:
depends on BR2_UCLIBC_VERSION_SNAPSHOT || \
external toolchain uses glibc or eglibc || \
crosstool-ng backend has glibc or eglibc selected
Would probably be more appropriate.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-22 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 14:10 [Buildroot] [PATCH] mongrel2: Needs a glibc or a uClibc-0.9.34-git based toolchain Markos Chandras
2013-05-22 14:43 ` Thomas Petazzoni [this message]
2013-05-22 14:57 ` Markos Chandras
2013-05-22 15:52 ` Thomas Petazzoni
2013-05-22 15:56 ` Markos Chandras
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=20130522164332.3a293c0d@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 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.