mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] ncurses 6.3 compile error
Date: Thu, 27 Oct 2022 20:50:48 +0200	[thread overview]
Message-ID: <CAH+2xPCOOnOHmP8kk=ovmWq0gi_GCnwJpSjzzmj8FSSOF_J-zQ@mail.gmail.com> (raw)

Hi

Has anyone experienced issues with ncurses 6.3?
Project is using OSELAS.Toolchain 2021.07 and ptxdist 2022.10.0.

/Bruno

-------8<-----------

-----------------------
target: ncurses.prepare
-----------------------

Removing files from sysroot...

configure: loading site script /usr/share/config.site
checking for ggrep... no
checking for grep... grep
checking for egrep... grep -E
Configuring NCURSES 6.3 ABI 6 (Thu Oct 27 11:56:05 UTC 2022)
checking for package version... 6.3
checking for package patch date... 20211021
checking build system type... x86_64-host-linux-gnu
checking host system type... arm-v7a-linux-gnueabihf
checking target system type... arm-v7a-linux-gnueabihf
Configuring for linux-gnueabihf
checking for fgrep... grep -F
checking for prefix... /usr
checking for arm-v7a-linux-gnueabihf-gcc... arm-v7a-linux-gnueabihf-gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether arm-v7a-linux-gnueabihf-gcc accepts -g... yes
checking version of arm-v7a-linux-gnueabihf-gcc... 7
checking if this is really Intel C compiler... no
checking if this is really Clang C compiler... no
checking for arm-v7a-linux-gnueabihf-gcc option to accept ANSI C... none needed
checking $CFLAGS variable... ok
checking $CC variable... ok
checking how to run the C preprocessor... arm-v7a-linux-gnueabihf-gcc -E
checking whether arm-v7a-linux-gnueabihf-gcc needs -traditional... no
checking whether arm-v7a-linux-gnueabihf-gcc understands -c and -o
together... yes
checking if you want to ensure bool is consistent with C++... no
checking if you want to build C++ binding and demo... no
checking if you want to build with Ada... no
checking if you want to install terminal database... yes
checking if you want to install manpages... no
checking if you want to build programs such as tic... no
checking if you want to build test-programs... no
checking if you wish to install curses.h... yes
checking for mawk... no
checking for gawk... gawk
checking for a BSD compatible install...
/usr/local/lib/ptxdist-2022.10.0/bin/install -c
checking for lint... no
checking for cppcheck... no
checking for splint... no
checking whether ln -s works... yes
checking if ln -s -f options work... yes
checking for long file names... yes
checking if you want to use pkg-config... yes
checking for arm-v7a-linux-gnueabihf-pkg-config...
/home/bth/gitlab/rockhopper/ptxdist/platform-tqma7/sysroot-cross/bin/arm-v7a-linux-gnueabihf-pkg-config
checking for /home/bth/gitlab/rockhopper/ptxdist/platform-tqma7/sysroot-cross/bin/arm-v7a-linux-gnueabihf-pkg-config
library directory... checking for first directory... none
checking if we should install .pc files for
/home/bth/gitlab/rockhopper/ptxdist/platform-tqma7/sysroot-cross/bin/arm-v7a-linux-gnueabihf-pkg-config...
yes
configure: error: expected a pathname, not ""
make: *** [/usr/local/lib/ptxdist-2022.10.0/rules/post/ptxd_make_world_prepare.make:24:
/home/bth/gitlab/rockhopper/ptxdist/platform-tqma7/state/ncurses.prepare]
Error 1



             reply	other threads:[~2022-10-27 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 18:50 Bruno Thomsen [this message]
2022-10-27 19:36 ` Christian Melki
2022-10-28 15:23   ` Michael Olbrich
2022-10-30 11:08     ` Bruno Thomsen
2022-10-30 14:19       ` Christian Melki
2022-10-30 19:47         ` Christian Melki
2022-11-21 16:07           ` Christian Melki
2022-11-22  5:54             ` Bruno Thomsen

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='CAH+2xPCOOnOHmP8kk=ovmWq0gi_GCnwJpSjzzmj8FSSOF_J-zQ@mail.gmail.com' \
    --to=bruno.thomsen@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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