[ptxdist] ncurses 6.3 compile error
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
Re: [ptxdist] ncurses 6.3 compile error
Hi Bruno, On 10/27/22 20:50, Bruno Thomsen wrote: > 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 "" Does your config.log contain more information? > 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 >
Re: [ptxdist] ncurses 6.3 compile error
On Thu, Oct 27, 2022 at 09:36:21PM +0200, Christian Melki wrote: > On 10/27/22 20:50, Bruno Thomsen wrote: > > 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 "" > > Does your config.log contain more information? Indeed, and do you have a local ncurses.make? The upstream rule explicitly specifies this path with --with-pkg-config-libdir=/usr/$(CROSS_LIB_DIR)/pkgconfig if I read the configure script correctly. Michael > > 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 > > > > > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
Re: [ptxdist] ncurses 6.3 compile error
Den fre. 28. okt. 2022 kl. 17.23 skrev Michael Olbrich
:
>
> On Thu, Oct 27, 2022 at 09:36:21PM +0200, Christian Melki wrote:
> > On 10/27/22 20:50, Bruno Thomsen wrote:
> > > 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 ""
> >
> > Does your config.log contain more information?
>
> Indeed, and do you have a local ncurses.make? The upstream rule explicitly
> specifies this path with
> --with-pkg-config-libdir=/usr/$(CROSS_LIB_DIR)/pkgconfig
> if I read the configure script correctly.
I am using the upstream rule as the project is migrated to 2022.10.0
and as far as I can see in git it's the same rule on master branch.
There are no rules/{host-,}ncurses.{in,make} in the project.
config.log is attached below.
configure:4300: error: expected a pathname, not ""
Looking in the configure script around line 4300,
the $PKG_CONFIG_LIBDIR variable is indeed empty.
So I will look into why with-pkg-config-libdir is not used.
/Bruno
8<-
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.52.20210509. Invocation command line was
$ ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
--libdir=/usr/lib --build=x86_64-host-linux-gnu
--host=arm-v7a-linux-gnueabihf --without-ada --without-cxx
--without-cxx-binding --enable-db-install --without-manpages
--without-progs --without-tack --without-tests --with-curses-h
--with-pkg-config-libdir=/usr/lib/pkgconfig --enable-pc-files
--enable-mixed-case --with
Re: [ptxdist] ncurses 6.3 compile error
On 10/30/22 12:08, Bruno Thomsen wrote: > error: expected a pathname, not "" Hmm. That home made horror show of configuration expects --enable-pc-files if I'm not mistaken. Can that be a clue to something? But it makes me wonder how on earth this worked in the first place? /C
Re: [ptxdist] ncurses 6.3 compile error
On 10/30/22 15:19, Christian Melki wrote: > On 10/30/22 12:08, Bruno Thomsen wrote: >> error: expected a pathname, not "" > > Hmm. That home made horror show of configuration expects > --enable-pc-files if I'm not mistaken. Can that be a clue to something? > But it makes me wonder how on earth this worked in the first place? > > /C > My bad. Ignore that. Somehow missed that the configure line already contained it. /C
Re: [ptxdist] ncurses 6.3 compile error
Hi Bruno, Did you solve your issue? For whatever reason, I tripped on the same error. Now, I can't follow the reasoning, the behavior, the patches or actually anything in the ncurses development. To me it's just a black box of strangeness. Either way. I concluded that for unidentified reasons I needed: https://invisible-mirror.net/archives/ncurses/6.3/ncurses-6.3-20211026.patch.gz added to the patchset. Literally the first in the series for 6.3. Maybe someone more versed can make sense of the discussion here: https://lists.gnu.org/archive/html/bug-ncurses/2021-10/msg00040.html Regards, Christian On 10/30/22 20:47, Christian Melki wrote: > On 10/30/22 15:19, Christian Melki wrote: >> On 10/30/22 12:08, Bruno Thomsen wrote: >>> error: expected a pathname, not "" >> >> Hmm. That home made horror show of configuration expects >> --enable-pc-files if I'm not mistaken. Can that be a clue to something? >> But it makes me wonder how on earth this worked in the first place? >> >> /C >> > > > My bad. Ignore that. Somehow missed that the configure line already > contained it. > > /C >
Re: [ptxdist] ncurses 6.3 compile error
Hi Christian, Den man. 21. nov. 2022 kl. 17.09 skrev Christian Melki : > > Hi Bruno, > > Did you solve your issue? I got the configure step working by adding autogen.sh symbolic link to patch directory. But then I hit a compile error. I saw that Fedora[1] carried some patches but did not yet test them in ptxdist context. At the moment I just use the old 6.2 version. /Bruno [1] https://src.fedoraproject.org/rpms/ncurses/tree/rawhide > > For whatever reason, I tripped on the same error. > Now, I can't follow the reasoning, the behavior, the patches or actually > anything in the ncurses development. To me it's just a black box of > strangeness. > > Either way. I concluded that for unidentified reasons I needed: > https://invisible-mirror.net/archives/ncurses/6.3/ncurses-6.3-20211026.patch.gz > added to the patchset. > > Literally the first in the series for 6.3. > > Maybe someone more versed can make sense of the discussion here: > https://lists.gnu.org/archive/html/bug-ncurses/2021-10/msg00040.html > > Regards, > Christian > > On 10/30/22 20:47, Christian Melki wrote: > > On 10/30/22 15:19, Christian Melki wrote: > >> On 10/30/22 12:08, Bruno Thomsen wrote: > >>> error: expected a pathname, not "" > >> > >> Hmm. That home made horror show of configuration expects > >> --enable-pc-files if I'm not mistaken. Can that be a clue to something? > >> But it makes me wonder how on earth this worked in the first place? > >> > >> /C > >> > > > > > > My bad. Ignore that. Somehow missed that the configure line already > > contained it. > > > > /C > > >
