From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] mongrel2: Needs a {e, }glibc or a uClibc-0.9.34-git based toolchain
Date: Thu, 23 May 2013 18:38:13 +0200 [thread overview]
Message-ID: <20130523183813.289449aa@skate> (raw)
In-Reply-To: <1369326481-18848-1-git-send-email-markos.chandras@gmail.com>
Dear Markos Chandras,
On Thu, 23 May 2013 17:28:01 +0100, Markos Chandras wrote:
> From: Markos Chandras <markos.chandras@imgtec.com>
>
> mongrel2 needs the {get,make,swap}context functions which are
> present in {e,}glibc and in the uClibc's master branch.
>
> Fixes:
> http://autobuild.buildroot.net/results/8e132a2b03a7b5ae94199db7db86883c05dca700/build-end.log
>
> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
--
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-23 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 16:28 [Buildroot] [PATCH v2] mongrel2: Needs a {e, }glibc or a uClibc-0.9.34-git based toolchain Markos Chandras
2013-05-23 16:38 ` Thomas Petazzoni [this message]
2013-05-23 20:31 ` 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=20130523183813.289449aa@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