From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc-ng: enable context functions
Date: Thu, 7 May 2015 06:01:16 +0200 [thread overview]
Message-ID: <20150507040116.GR8309@waldemar-brodkorb.de> (raw)
In-Reply-To: <20150506212318.6025af52@free-electrons.com>
Hi Thomas,
Thomas Petazzoni wrote,
> Dear Waldemar Brodkorb,
>
> On Wed, 6 May 2015 19:50:30 +0200, Waldemar Brodkorb wrote:
> > For mongrel2/libsigsegv we need to enable this in the uClibc-ng config.
> > Tested with ARM:
> >
> > file output/target/usr/bin/mongrel2
> > output/target/usr/bin/mongrel2: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped
> >
> > Should fix:
> > http://autobuild.buildroot.net/results/a144bc6024415a5272c3cbe60ff636d078d0a555/
> > http://autobuild.buildroot.net/results/00195d89a115a314bf4916af127407f61cd1b418/
> > http://autobuild.buildroot.net/results/5ee7e83ebcfa43f6ee0a2a8b9f40f1ae84664aca/
> >
> > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> > ---
> > package/uclibc/uClibc-ng.config | 1 +
> > 1 file changed, 1 insertion(+)
>
> We don't have this option enabled in uClibc-0.9.33.config. Should I
> assume that it's because this option doesn't exist in the 0.9.33.x
> uClibc branch?
Right, it was added later:
http://git.uclibc.org/uClibc/commit/extra/Configs/Config.in?id=a8dc90eaaa5e6474beac828558d969b1aafee4af
> Also, why don't we have this option enabled in uClibc-snapshot.config?
I don't know how often this file get updated?
BTW: These functions are only available for arm/mips/x86/x86_64.
So mongrel2/libsigsegv need to be fixed to these, when uClibc is
choosen.
best regards
Waldemar
next prev parent reply other threads:[~2015-05-07 4:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 17:50 [Buildroot] [PATCH] uclibc-ng: enable context functions Waldemar Brodkorb
2015-05-06 19:23 ` Thomas Petazzoni
2015-05-06 22:10 ` Yann E. MORIN
2015-05-07 4:01 ` Waldemar Brodkorb [this message]
2015-05-07 7:25 ` 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=20150507040116.GR8309@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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