From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pakage/erlang: fix host build without termcap (curses) library
Date: Tue, 18 Nov 2014 09:31:52 +0100 [thread overview]
Message-ID: <20141118093152.70fa0bd7@free-electrons.com> (raw)
In-Reply-To: <1416263596-11129-1-git-send-email-yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Mon, 17 Nov 2014 23:33:16 +0100, Yann E. MORIN wrote:
> Cc-ing Nathaniel, as all failures happen on his build server. Thomas and
> Nathaniel, could you please review the setting of that autobuild server?
> And the others as well?
We already discussed this on the mailing list some time ago.
Nathaniel's build server is the only one where libncurses-dev is not
installed in the system. And since libncurses-dev is not part of our
mandatory dependencies (someone could very well use gconfig or xconfig
only, for example), we thought that keeping Nathaniel's configuration
as is was a good way of catching the cases where we have a missing
dependency on host-ncurses.
I remember we even had a discussion to decide whether we should build
host-ncurses in such cases, or whether we should make libncurses-dev a
hard dependency of Buildroot, and Peter decided that building
host-ncurses was the right solution.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-18 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 22:33 [Buildroot] [PATCH] pakage/erlang: fix host build without termcap (curses) library Yann E. MORIN
2014-11-18 7:59 ` Nathaniel Roach
2014-11-18 17:46 ` Yann E. MORIN
2014-11-18 8:31 ` Thomas Petazzoni [this message]
2014-11-18 17:49 ` Yann E. MORIN
2014-11-18 20:55 ` 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=20141118093152.70fa0bd7@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