This requires investigating where setupterm() is supposed to come from
and why it isn't picked up. It helps to set up a plain poky build with
one of the qemu machines to get a stable working reference point.
Alex
On Thu, 13 Jun 2024 at 11:01, Mayank Pandey via lists.yoctoproject.org
<pandeymayank96=gmail....@lists.yoctoproject.org> wrote:
>
> Hello Yocto experts
>
> I am trying to upgrade my custom bsp layer working on Yocto 4.0 (kirkstone)
> branch to Yocto 5.0 (scarthgap). I have made all the necessary modifications
> to the custom recipes based on the 5.0 patch notes. I am facing an error with
> the python3 version of scarthgap not being able to build ncurses module due
> to implicit declaration error. I tried the same with 4.3 branch (nanbield) as
> well, which gave me the same error. The error snippet is as follows (error is
> from python3 do_install step)
>
> NOTE: Skipping as already exists in sysroot: ['openssl', 'expat',
> 'gettext-minimal-native', 'glibc', 'libxcrypt', 'ncurses',
> 'util-linux-libuuid', 'zlib', 'binutils-cross-aarch64', 'cmake-native',
> 'gcc-cross-aarch64', 'gcc-runtime', 'libgcc', 'libedit', 'libtool-cross',
> 'libtool-native', 'm4-native', 'opkg-utils', 'quilt-native', 'bzip2',
> 'libnsl2', 'libtirpc', 'texinfo-dummy-native', 'xz', 'linux-libc-headers',
> 'gdbm', 'libffi', 'sqlite3', 'openssl-native', 'expat-native',
> 'ncurses-native', 'util-linux-libuuid-native', 'zlib-native',
> 'autoconf-archive-native', 'autoconf-native', 'automake-native',
> 'flex-native', 'gnu-config-native', 'libedit-native', 'make-native',
> 'patch-native', 'perl-native', 'pkgconfig-native', 'pseudo-native',
> 'python3-native', 'bzip2-native', 'libnsl2-native', 'libtirpc-native',
> 'xz-native', 'zstd-native', 'attr-native', 'gdbm-native', 'gmp-native',
> 'libffi-native', 'libmpc-native', 'mpfr-native', 'sqlite3-native']DEBUG:
> Python function extend_recipe_sysroot finishedDEBUG: Executing python
> function autotools_aclocalsDEBUG: SITE files ['endian-little', 'bit-64',
> 'arm-common', 'arm-64', 'common-linux', 'common-glibc', 'aarch64-linux',
> 'common']DEBUG: Python function autotools_aclocals finishedDEBUG: Executing
> shell function do_installFailed to build these modules:_curses
>
>
> Now I dug a little deeper to get the error from the do_install step, and
> found that the _curses module had failed in compilation step itself but the
> compilation continuer, and then it failed in the do_install step.
> The do_compile logs are as below:
>
> /dvs/container/cm/git-master_yocto/yocto/build/tmp/work/armv8a-gnu-linux/python3/3.11.5/Python-3.11.5/Modules/_cursesmodule.c:3398:35:
> error: implicit declaration of function 'setupterm'; did you mean
> 'set_term'? [-Werror=implicit-function-declaration] 3398 | if
> (!initialised_setupterm && setupterm((char *)term, fd, &err) == ERR) { |
> ^~~~~~~~~ |
> set_term
>
>
> Does anyone know what could be the root cause of this issue?
> One more thing to not is that the error is intermittent - but with a very low
> passing rate of ~5-10% (90-95 % of the build fails with the upgrade).
> Thanks for any inputs
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63338): https://lists.yoctoproject.org/g/yocto/message/63338
Mute This Topic: https://lists.yoctoproject.org/mt/106648183/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
