Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pinentry: fix ncurses' unsafe header path
Date: Sat, 28 Feb 2015 00:06:00 +0100	[thread overview]
Message-ID: <87vbinymxz.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1425055087-9334-1-git-send-email-Vincent.Riera@imgtec.com> (Vicente Olivert Riera's message of "Fri, 27 Feb 2015 16:38:07 +0000")

>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:

 > pinentry sets the NCURSES_INCLUDE variable in the Makefile to
 > /usr/include/ncurses and that causes problems when cross-compiling
 > because it fails with an error like this one:

 > Making all in curses
 > make[3]: Entering directory `/br/output/build/pinentry-0.9.0/curses'
 > /br/output/host/usr/bin/mips64el-ctng_n64-linux-gnu-gcc -DHAVE_CONFIG_H
 > -I. -I..  -I/usr/include/ncursesw -I../pinentry -D_LARGEFILE_SOURCE
 > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall  -D_LARGEFILE_SOURCE
 > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64   -Os  -Wall -Wcast-align
 > -Wshadow -Wstrict-prototypes -Wno-pointer-sign -c pinentry-curses.c
 > mips64el-ctng_n64-linux-gnu-gcc: ERROR: unsafe header/library path used
 > in cross-compilation: '/usr/include/ncursesw'
 > make[3]: *** [pinentry-curses.o] Error 1

 > Fixes:

 >   http://autobuild.buildroot.net/results/5b9/5b9b53a37f7cf4bab4d989f852726a0f0885605f/

 > Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
 > ---
 >  package/pinentry/pinentry.mk |    1 +
 >  1 files changed, 1 insertions(+), 0 deletions(-)

 > diff --git a/package/pinentry/pinentry.mk b/package/pinentry/pinentry.mk
 > index f34cc0e..b38ebb4 100644
 > --- a/package/pinentry/pinentry.mk
 > +++ b/package/pinentry/pinentry.mk
 > @@ -21,6 +21,7 @@ endif
 
 >  # pinentry-ncurses backend
 >  ifeq ($(BR2_PACKAGE_PINENTRY_NCURSES),y)
 > +PINENTRY_CONF_ENV += inetutils_cv_includedir_ncurses=$(STAGING_DIR)/usr/include/ncurses

Thanks, but we don't actually install anything under
$(STAGING_DIR)/usr/include/ncurses (it is directly in
$(STAGING_DIR)/usr/include). Looking at the configure script, the
documented way of not adding a special -I for ncurses is simply to pass
--with-ncurses-include-dir=none so I've changed it to use that instead.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2015-02-27 23:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 16:38 [Buildroot] [PATCH] pinentry: fix ncurses' unsafe header path Vicente Olivert Riera
2015-02-27 23:06 ` Peter Korsgaard [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=87vbinymxz.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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