From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] slang: fix static link with ncurses
Date: Sat, 5 Mar 2016 15:17:29 +0100 [thread overview]
Message-ID: <20160305151729.66a74f70@free-electrons.com> (raw)
In-Reply-To: <4aa51349a8c68f15bfc5ba169eeea9c6e9959128.1456834855.git.baruch@tkos.co.il>
Dear Baruch Siach,
On Tue, 1 Mar 2016 14:20:55 +0200, Baruch Siach wrote:
> slang does forgets ncurses that is a dependency of readline when linking the
> slsh binary. Correct this.
>
> While at it, also make sure to use staging ncurses5-config script and not the
> host one.
>
> Fixes:
> http://autobuild.buildroot.net/results/1dc/1dc52048254c32a24070fef1c1039cebb32e7ac1/
> http://autobuild.buildroot.net/results/c17/c176511cbb147c2d8cb0ec0ff3c1612ce8971cb8/
> http://autobuild.buildroot.net/results/78d/78dc2ba07b1d7f888aab94e223f3e0b1a1df3af5/
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/slang/slang.mk | 4 ++++
> 1 file changed, 4 insertions(+)
I've marked this patch as Superseded in patchwork, as I believe it was
superseded by your patch "[PATCH] slang: fix static link with
readline", even though the title has changed and v2 was not indicated.
Let me know if this isn't correct.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-03-05 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 12:20 [Buildroot] [PATCH] slang: fix static link with ncurses Baruch Siach
2016-03-01 16:43 ` Peter Korsgaard
2016-03-01 18:15 ` Baruch Siach
2016-03-05 14:17 ` 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=20160305151729.66a74f70@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