Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/sngrep: add missing ncurses dependencies
Date: Sat, 18 Feb 2017 17:03:47 +0100	[thread overview]
Message-ID: <17795fb2-39c2-fe6d-5573-58fc0b4f6c94@gmail.com> (raw)
In-Reply-To: <20170218164928.59e0f1c5@free-electrons.com>

Hi Thomas, All,

Le 18/02/2017 ? 16:49, Thomas Petazzoni a ?crit :
> Hello,
> 
> On Sat, 18 Feb 2017 16:43:33 +0100, Romain Naour wrote:
>> ncurses panel and forms libraries are needed to build sngrep, otherwise
>> the configure script report the following errors:
>>
>> Without panel library:
>> checking ncurses.h usability... yes
>> checking ncurses.h presence... yes
>> checking for ncurses.h... yes
>> checking for initscr in -lncurses... yes
>> checking for new_panel in -lpanel... no
>> configure: error:  You need to have ncurses panel library installed to compile sngrep.
>>
>> Without form library:
>> checking ncurses.h usability... yes
>> checking ncurses.h presence... yes
>> checking for ncurses.h... yes
>> checking for initscr in -lncurses... yes
>> checking for new_panel in -lpanel... yes
>> checking for new_form in -lform... no
>> configure: error:  You need to have ncurses forms library installed to compile sngrep.
>>
>> Fixes:
>> http://autobuild.buildroot.net/results/ee5/ee58cd4252e4da95e9bd025ced9ad3ba0fb7cb08
>>
>> Signed-off-by: Romain Naour <romain.naour@gmail.com>
>> Cc: Adam Duskett <aduskett@codeblue.com>
> 
> I still believe there is a bigger issue. I can build sngrep here
> without those additional ncurses options and it builds fine.
> 
> In fact, our ncurses package is completely broken. It always installs
> *all* the libraries to staging, and all what
> BR2_PACKAGE_NCURSES_TARGET_PANEL or BR2_PACKAGE_NCURSES_TARGET_FORM is
> doing is installing the libraries to the target. So you end up in a
> situation where some libraries are available in staging, and therefore
> detected by the build process of other packages, but will in fact not
> be present on the target.
> 
> However, I still don't understand how it can fail on the autobuilders.
> Have you been able to reproduce the issues locally?

Yes, I'm able to reproduce the issues locally and I had to add these two
variables to fix these two issues...

> 
> Even though yes this patch probably fixes the issue, there's an
> underlying issue which I would like to also understand and fix.

Agree, something is weird here.

Best regards,
Romain

> 
> Thanks,
> 
> Thomas
> 

  reply	other threads:[~2017-02-18 16:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18 15:43 [Buildroot] [PATCH] package/sngrep: add missing ncurses dependencies Romain Naour
2017-02-18 15:49 ` Thomas Petazzoni
2017-02-18 16:03   ` Romain Naour [this message]
2017-02-18 17:23     ` Thomas Petazzoni
2017-02-18 18:21   ` Bernd Kuhls
2017-02-18 19:09     ` Romain Naour
2017-02-19  9:01     ` Thomas Petazzoni
2017-02-21 21:41 ` 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=17795fb2-39c2-fe6d-5573-58fc0b4f6c94@gmail.com \
    --to=romain.naour@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox