All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathaniel Roach <nroach44@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pakage/erlang: fix host build without termcap (curses) library
Date: Tue, 18 Nov 2014 15:59:56 +0800	[thread overview]
Message-ID: <546AFC7C.1060501@gmail.com> (raw)
In-Reply-To: <1416263596-11129-1-git-send-email-yann.morin.1998@free.fr>

On 18/11/14 06:33, 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?
>
> It seems legit ncurses is missing on a build server, but we did not
notice,
> because we do require it for menuconfig and nconfig, so virtually everyone
> has it, and it is most probably installed on other autobuild servers
> because owners want to be able to run menuconfig on them to debug stuff.
>
> Care to have a look, please?
>
> Regards,
> Yann E. MORIN.

I haven't installed libncurses-dev per the discussion we had a few
weeks/months back. (Basically only use the system's ncurses for 'make
*config', and in all other cases build it)

I haven't heard otherwise, and this is also causing failures in
host-mysql (IIRC).

If you both believe that I should install it, I will, but I still
believe it is better to build host-ncurses.

Thanks, Nathaniel.

  reply	other threads:[~2014-11-18  7:59 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 [this message]
2014-11-18 17:46   ` Yann E. MORIN
2014-11-18  8:31 ` Thomas Petazzoni
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=546AFC7C.1060501@gmail.com \
    --to=nroach44@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.