From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gauche: fix getcontext not solved error on link
Date: Mon, 16 Nov 2015 23:03:22 +0100 [thread overview]
Message-ID: <20151116230322.0f6137a8@free-electrons.com> (raw)
In-Reply-To: <201511131005.tADA5pt9030611@ms-omx02.plus.so-net.ne.jp>
Hiroshi,
On Fri, 13 Nov 2015 19:05:51 +0900, Hiroshi Kawashima wrote:
> This patch is ported from bdwgc package.
> Gauche use internal boehm gc so it has same problem.
>
> I touch configure directly instead of configure.ac because autoreconf
> failed by version mismatch of autotools.
>
> Will fix:
> http://autobuild.buildroot.org/results/8c6/8c6ce526735a36b8c8b4c6047e3c69039c4527cb//
> http://autobuild.buildroot.org/results/894/89460829a737a4dab19103f7a46905636420b0a8//
>
> Signed-off-by: Hiroshi Kawashima <kei-k@ca2.so-net.ne.jp>
> ---
> ...ac-add-check-for-NO_GETCONTEXT-definition.patch | 61 ++++++++++++++++++++
> 1 files changed, 61 insertions(+), 0 deletions(-)
> create mode 100644 package/gauche/0002-gc-configure.ac-add-check-for-NO_GETCONTEXT-definition.patch
Applied to master after tweaking the commit log and patch description,
thanks.
Also, please report to upstream that their configure.ac doesn't work
with modern version of the autotools, they should fix that up.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-11-16 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 10:05 [Buildroot] [PATCH] package/gauche: fix getcontext not solved error on link Hiroshi Kawashima
2015-11-16 7:00 ` Arnout Vandecappelle
2015-11-16 12:33 ` Hiroshi Kawashima
2015-11-16 14:04 ` Arnout Vandecappelle
2015-11-16 22:03 ` Thomas Petazzoni [this message]
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=20151116230322.0f6137a8@free-electrons.com \
--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