Date   

Re: task do_patch does not exist

Alexander Kanavin
 

I think you need to move the recipe from a workspace to the layer first with 'devtool finish'. When the recipe is in a workspace, it's taking the source code from the workspace as well, and additional patches aren't used.

Alex


On Thu, 2 Sept 2021 at 10:10, Ivan Riabtsov <ivriabtsov@...> wrote:
Hello. I created a recipe with the following command:

$ devtool add  mosquitto
https://mosquitto.org/files/source/mosquitto-2.0.11.tar.gz

i got the file:

ivr@home-machine:~/work/yocto/build
$ cat workspace/recipes/mosquitto/mosquitto_2.0.11.bb
# Recipe created by recipetool
# This is the basis of a recipe and may need further editing in order
to be fully functional.
# (Feel free to remove these comments when editing.)

# WARNING: the following LICENSE and LIC_FILES_CHKSUM values are best
guesses - it is
# your responsibility to verify that the values are complete and correct.
#
# The following license files were not able to be identified and are
# represented as "Unknown" below, you will need to check them yourself:
#   LICENSE.txt
#
LICENSE = "Unknown"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=ca9a8f366c6babf593e374d0d7d58749"


SRC_URI = "https://mosquitto.org/files/source/mosquitto-${PV}.tar.gz"
SRC_URI[md5sum] = "638d801e6aac611b41de76d030951612"
SRC_URI[sha256sum] =
"7b36a7198bce85cf31b132f5c6ee36dcf5dadf86fb768501eb1e11ce95d4f78a"
SRC_URI += " file://0001-arch-makefile-variable.patch"

# NOTE: unable to map the following CMake package dependencies: cJSON
libwebsockets
# NOTE: the following library dependencies are unknown, ignoring: systemd
#       (this is based on recipes that have previously been built and packaged)
DEPENDS = "openssl"

inherit cmake pkgconfig

# Specify any options you want to pass to cmake using EXTRA_OECMAKE:
EXTRA_OECMAKE = ""

do_patch() {
    patch -p1 -d ${WORKDIR} < ${WORKDIR}/0001-arch-makefile-variable.patch
}

i added the line:
SRC_URI += " file://0001-arch-makefile-variable.patch"
and i try to run bitbake -c patch mosquitto
i got the ERROR: Task do_patch does not exist for target mosquitto
I added the lines:
do_patch() {
    patch -p1 -d ${WORKDIR} < ${WORKDIR}/0001-arch-makefile-variable.patch
}

but i got the same error.

Please tell me what I am doing wrong? Before, when I created recipes
by hand, it was enough for me to add the line SRC_URI + =
"file://some-patch.patch" and the do_patch task itself appeared and
was executed




task do_patch does not exist

Ivan Riabtsov <ivriabtsov@...>
 

Hello. I created a recipe with the following command:

$ devtool add mosquitto
https://mosquitto.org/files/source/mosquitto-2.0.11.tar.gz

i got the file:

ivr@home-machine:~/work/yocto/build
$ cat workspace/recipes/mosquitto/mosquitto_2.0.11.bb
# Recipe created by recipetool
# This is the basis of a recipe and may need further editing in order
to be fully functional.
# (Feel free to remove these comments when editing.)

# WARNING: the following LICENSE and LIC_FILES_CHKSUM values are best
guesses - it is
# your responsibility to verify that the values are complete and correct.
#
# The following license files were not able to be identified and are
# represented as "Unknown" below, you will need to check them yourself:
# LICENSE.txt
#
LICENSE = "Unknown"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=ca9a8f366c6babf593e374d0d7d58749"


SRC_URI = "https://mosquitto.org/files/source/mosquitto-${PV}.tar.gz"
SRC_URI[md5sum] = "638d801e6aac611b41de76d030951612"
SRC_URI[sha256sum] =
"7b36a7198bce85cf31b132f5c6ee36dcf5dadf86fb768501eb1e11ce95d4f78a"
SRC_URI += " file://0001-arch-makefile-variable.patch"

# NOTE: unable to map the following CMake package dependencies: cJSON
libwebsockets
# NOTE: the following library dependencies are unknown, ignoring: systemd
# (this is based on recipes that have previously been built and packaged)
DEPENDS = "openssl"

inherit cmake pkgconfig

# Specify any options you want to pass to cmake using EXTRA_OECMAKE:
EXTRA_OECMAKE = ""

do_patch() {
patch -p1 -d ${WORKDIR} < ${WORKDIR}/0001-arch-makefile-variable.patch
}

i added the line:
SRC_URI += " file://0001-arch-makefile-variable.patch"
and i try to run bitbake -c patch mosquitto
i got the ERROR: Task do_patch does not exist for target mosquitto
I added the lines:
do_patch() {
patch -p1 -d ${WORKDIR} < ${WORKDIR}/0001-arch-makefile-variable.patch
}

but i got the same error.

Please tell me what I am doing wrong? Before, when I created recipes
by hand, it was enough for me to add the line SRC_URI + =
"file://some-patch.patch" and the do_patch task itself appeared and
was executed


Re: gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool?

Peter Bergin
 

Hi Matthias,

On 2021-09-01 17:11, Matthias Klein wrote:
Hello Peter,

I'm not sure it's that simple.
Sorry for my quick and a bit oversimplified response. I did my first build on an older version (3.20) where ubxtool was not built but present in the repo root. I see now that in 3.23 gpsd have changed concept and client/ubxtool.py.in is mangled through the build system to fill in some stuff and produce the ubxtool script.
To me it looks like the recipe has bugs in python area, or my environment / build is causing problems.
In the log.do_compile file I see messages which make me wonder:

Checking whether python program exists...no
Target Python doesn't exist - disabling Python.
python = False (default True): build Python support and modules.
GPS regression tests suppressed because socket_export or python is off.

It looks to me that everything Python specific is disabled.
Therefore I am missing on the target e.g. also the following file which should be generated:

/usr/lib/python3.9/site-packages/gps/__init__.py
/usr/lib/python3.9/site-packages/gps/gps.py

Can anyone confirm this?
Confirmed!

The issue is that the package gpsd requires /usr/bin/python to be present as described in the documentation (https://gitlab.com/gpsd/gpsd/-/blob/master/build.adoc#user-content-quick-start). This is not the case in Yocto when using python3native bbclass. As described in the documentation it is possible to add a symlink called /usr/bin/python to the python interpreter in the sysroot. You can do this by adding:

    ln -sf python3-native/python3 ${STAGING_BINDIR_NATIVE}/python

When scons finds /usr/bin/python the python packages are also built in gpsd. Then you can continue to install and package ubxtool.

Best regards,
/Peter


Re: porting riscv on openjdk

Khem Raj
 

On Wed, Sep 1, 2021 at 7:22 AM <abhishek.kumar@...> wrote:

hi sir
i am trying to build openjdk on riscv but i am facing problem can you suggest what steps i need to follow

root@exaleapsemi-3:~/abhi/jdk# bash configure
configure: Configuration created at Thu Aug 26 08:50:43 UTC 2021.
checking for basename... /usr/bin/basename
checking for dirname... /usr/bin/dirname
checking for file... /usr/bin/file
checking for ldd... no
checking for bash... /bin/bash
checking for cat... /bin/cat
checking for chmod... /bin/chmod
checking for cp... /bin/cp
checking for cut... /usr/bin/cut
checking for date... /bin/date
checking for gdiff... [not found]
checking for diff... /usr/bin/diff
checking for echo... echo [builtin]
checking for expr... /usr/bin/expr
checking for find... /usr/bin/find
checking for gunzip... /bin/gunzip
checking for pigz... [not found]
checking for gzip... /bin/gzip
checking for head... /usr/bin/head
checking for ln... /bin/ln
checking for ls... /bin/ls
checking for gmkdir... [not found]
checking for mkdir... /bin/mkdir
checking for mktemp... /bin/mktemp
checking for mv... /bin/mv
checking for gawk... /usr/bin/gawk
checking for printf... printf [builtin]
checking for rm... /bin/rm
checking for rmdir... /bin/rmdir
checking for sh... /bin/sh
checking for sort... /usr/bin/sort
checking for tail... /usr/bin/tail
checking for gtar... /bin/gtar
checking for tee... /usr/bin/tee
checking for touch... /bin/touch
checking for tr... /usr/bin/tr
checking for uname... /bin/uname
checking for wc... /usr/bin/wc
checking for xargs... /usr/bin/xargs
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for a sed that does not truncate output... /bin/sed
checking for df... /bin/df
checking for nice... /bin/nice
checking for greadlink... [not found]
checking for readlink... /usr/bin/readlink
checking for cygpath... [not found]
checking for wslpath... [not found]
checking for lsb_release... [not found]
checking for cmd.exe... [not found]
checking for cmp... /usr/bin/cmp
checking for uniq... /usr/bin/uniq
checking build system type... riscv64-unknown-linux-gnu
checking host system type... riscv64-unknown-linux-gnu
checking target system type... riscv64-unknown-linux-gnu
checking openjdk-build os-cpu... linux-riscv64
checking openjdk-build C library... gnu
checking openjdk-target os-cpu... linux-riscv64
checking openjdk-target C library... gnu
checking compilation type... native
checking for top-level directory... /home/root/abhi/jdk
checking if custom source is suppressed (openjdk-only)... disabled, default
checking for --enable-debug... disabled, default
checking which debug level to use... release
checking which variants of the JVM to build... server
checking if absolute paths should be allowed in the build output... no, release build
checking for sysroot...
checking for toolchain path...
checking for extra path...
checking where to store configuration... in default location
checking what configuration name to use... linux-riscv64-server-release
checking for zypper... [not found]
checking for apt-get... /usr/bin/apt-get
checking for pandoc... [not found]
checking for gmake... [not found]
checking for make... /usr/bin/make
configure: Testing potential make at /usr/bin/make, found using make in PATH
configure: Using GNU make at /usr/bin/make (version: GNU Make 4.3)
checking if make --output-sync is supported... yes
checking for output-sync value... none
checking if find supports -delete... yes
checking what type of tar was found... gnu
checking that grep (/bin/grep) -Fx handles empty lines in the pattern list correctly... yes
checking for unzip... /usr/bin/unzip
checking for zip... /usr/bin/zip
checking for greadelf... [not found]
checking for readelf... /usr/bin/readelf
checking for dot... [not found]
checking for hg... [not found]
checking for git... /usr/bin/git
checking for stat... /bin/stat
checking for time... time [builtin]
checking for flock... /usr/bin/flock
checking for dtrace... [not found]
checking for gpatch... [not found]
checking for patch... /usr/bin/patch
checking for ulimit... ulimit [builtin]
checking bash version... 5.0.18
checking if bash supports pipefail... yes
checking if bash supports errexit (-e)... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for default LOG value...
checking if packaged modules are kept... enabled, default
checking for version string... 18-internal+0-adhoc.root.jdk
checking for javac... [not found]
checking for java... [not found]
configure: Could not find a valid Boot JDK. OpenJDK distributions are available at http://jdk.java.net/.
configure: This might be fixed by explicitly setting --with-boot-jdk
configure: error: Cannot continue
configure exiting with result code 1
root@exaleapsemi-3:~/abhi/jdk# apt-get install libcups2-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libcups2-dev
root@exaleapsemi-3:~/abhi/jdk# apt-get install libfontconfig1-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libfontconfig1-dev
root@exaleapsemi-3:~/abhi/jdk# apt-get install libasound2-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libasound2-dev
root@exaleapsemi-3:~/abhi/jdk# bash configure
configure: Configuration created at Thu Aug 26 08:52:37 UTC 2021.
checking for basename... /usr/bin/basename
checking for dirname... /usr/bin/dirname
checking for file... /usr/bin/file
checking for ldd... no
checking for bash... /bin/bash
checking for cat... /bin/cat
checking for chmod... /bin/chmod
checking for cp... /bin/cp
checking for cut... /usr/bin/cut
checking for date... /bin/date
checking for gdiff... [not found]
checking for diff... /usr/bin/diff
checking for echo... echo [builtin]
checking for expr... /usr/bin/expr
checking for find... /usr/bin/find
checking for gunzip... /bin/gunzip
checking for pigz... [not found]
checking for gzip... /bin/gzip
checking for head... /usr/bin/head
checking for ln... /bin/ln
checking for ls... /bin/ls
checking for gmkdir... [not found]
checking for mkdir... /bin/mkdir
checking for mktemp... /bin/mktemp
checking for mv... /bin/mv
checking for gawk... /usr/bin/gawk
checking for printf... printf [builtin]
checking for rm... /bin/rm
checking for rmdir... /bin/rmdir
checking for sh... /bin/sh
checking for sort... /usr/bin/sort
checking for tail... /usr/bin/tail
checking for gtar... /bin/gtar
checking for tee... /usr/bin/tee
checking for touch... /bin/touch
checking for tr... /usr/bin/tr
checking for uname... /bin/uname
checking for wc... /usr/bin/wc
checking for xargs... /usr/bin/xargs
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for a sed that does not truncate output... /bin/sed
checking for df... /bin/df
checking for nice... /bin/nice
checking for greadlink... [not found]
checking for readlink... /usr/bin/readlink
checking for cygpath... [not found]
checking for wslpath... [not found]
checking for lsb_release... [not found]
checking for cmd.exe... [not found]
checking for cmp... /usr/bin/cmp
checking for uniq... /usr/bin/uniq
checking build system type... riscv64-unknown-linux-gnu
checking host system type... riscv64-unknown-linux-gnu
checking target system type... riscv64-unknown-linux-gnu
checking openjdk-build os-cpu... linux-riscv64
checking openjdk-build C library... gnu
checking openjdk-target os-cpu... linux-riscv64
checking openjdk-target C library... gnu
checking compilation type... native
checking for top-level directory... /home/root/abhi/jdk
checking if custom source is suppressed (openjdk-only)... disabled, default
checking for --enable-debug... disabled, default
checking which debug level to use... release
checking which variants of the JVM to build... server
checking if absolute paths should be allowed in the build output... no, release build
checking for sysroot...
checking for toolchain path...
checking for extra path...
checking where to store configuration... in default location
checking what configuration name to use... linux-riscv64-server-release
checking for zypper... [not found]
checking for apt-get... /usr/bin/apt-get
checking for pandoc... [not found]
checking for gmake... [not found]
checking for make... /usr/bin/make
configure: Testing potential make at /usr/bin/make, found using make in PATH
configure: Using GNU make at /usr/bin/make (version: GNU Make 4.3)
checking if make --output-sync is supported... yes
checking for output-sync value... none
checking if find supports -delete... yes
checking what type of tar was found... gnu
checking that grep (/bin/grep) -Fx handles empty lines in the pattern list correctly... yes
checking for unzip... /usr/bin/unzip
checking for zip... /usr/bin/zip
checking for greadelf... [not found]
checking for readelf... /usr/bin/readelf
checking for dot... [not found]
checking for hg... [not found]
checking for git... /usr/bin/git
checking for stat... /bin/stat
checking for time... time [builtin]
checking for flock... /usr/bin/flock
checking for dtrace... [not found]
checking for gpatch... [not found]
checking for patch... /usr/bin/patch
checking for ulimit... ulimit [builtin]
checking bash version... 5.0.18
checking if bash supports pipefail... yes
checking if bash supports errexit (-e)... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for default LOG value...
checking if packaged modules are kept... enabled, default
checking for version string... 18-internal+0-adhoc.root.jdk
checking for javac... [not found]
checking for java... [not found]
configure: Could not find a valid Boot JDK. OpenJDK distributions are available at http://jdk.java.net/.
configure: This might be fixed by explicitly setting --with-boot-jdk
configure: error: Cannot continue
configure exiting with result code 1


Re: Issue baking a new layer for a custom kernel #kernel

Khem Raj
 

ensure that you are using same release branches for all layer repos
generally RDEPENDS and RRECOMMENDS should be replaced with
RDEPENDS_<pkgname> etc.

On Wed, Sep 1, 2021 at 7:22 AM nagesh shamnur <nagesh.shamnur@...> wrote:

Hi Group,
I am trying to add a new layer for a custom RTOS which supports RISCV32 architecture. When i run bitbake i bumped into following error:
"
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb: QA Issue: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb: Variable RDEPENDS is set as not being package specific, please fix this. [pkgvarcheck]
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb: QA Issue: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb: Variable RRECOMMENDS is set as not being package specific, please fix this. [pkgvarcheck]
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb: Fatal QA errors found, failing task.
ERROR: Failed to parse recipe: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb
WARNING: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-yappi_1.0.bb: Cooker received SIGTERM, shutting down...
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-werkzeug_1.0.0.bb: QA Issue: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-werkzeug_1.0.0.bb: Variable RDEPENDS is set as not being package specific, please fix this. [pkgvarcheck]
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-werkzeug_1.0.0.bb: QA Issue: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-werkzeug_1.0.0.bb: Variable RRECOMMENDS is set as not being package specific, please fix this. [pkgvarcheck]
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-werkzeug_1.0.0.bb: Fatal QA errors found, failing task.
WARNING: Cooker received SIGTERM, shutting down...
WARNING: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zipp_0.6.0.bb: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...

Summary: There were 12 WARNING messages shown.
Summary: There were 7 ERROR messages shown, returning a non-zero exit code.
"

Looking for the exact line which might have created a problem, found out that the issue is happening in the following line
"PACKAGES =. "${PN}-test " from the file ./meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb.

i have tried the following options, but none of them have helped in solving the issue.
1) I suspected that missing python3native might have resulted in the problem and included "inherit python3native" in my recipe file,
2) Also checked for presence of RDEPENDS in my recipe file as below: "LAYERDEPENDS_xxx ="core meta-python"

Please suggest a way out of this issue.

Thanks!




Re: gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool?

Matthias Klein
 

Hello Peter,

I'm not sure it's that simple.

To me it looks like the recipe has bugs in python area, or my environment / build is causing problems.
In the log.do_compile file I see messages which make me wonder:

Checking whether python program exists...no
Target Python doesn't exist - disabling Python.
python = False (default True): build Python support and modules.
GPS regression tests suppressed because socket_export or python is off.

It looks to me that everything Python specific is disabled.
Therefore I am missing on the target e.g. also the following file which should be generated:

/usr/lib/python3.9/site-packages/gps/__init__.py
/usr/lib/python3.9/site-packages/gps/gps.py

Can anyone confirm this?

Best regards,
Matthias

-----Ursprüngliche Nachricht-----
Von: Peter Bergin <peter@...>
Gesendet: Mittwoch, 1. September 2021 15:15
An: Matthias Klein <matthias.klein@...>; yocto@...
Betreff: Re: [yocto] gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool?

Hi Matthias,

On 2021-09-01 12:33, Matthias Klein wrote:
Hello,

is it somehow possible to add the ubxtool in the gpsd-utils package?

(I use the current master branch)
gpsd recipe is located in meta-oe. As the ubxtool file is present in the build it is possible to add it. Just make sure it is installed in the do_install step and then that the file is added to FILES_gps-utils variable.

Best regards,
/Peter


porting riscv on openjdk

abhishek.kumar@...
 

hi sir
i am trying to build openjdk on riscv but i am facing problem can you suggest what steps i need to follow

root@exaleapsemi-3:~/abhi/jdk# bash configure
configure: Configuration created at Thu Aug 26 08:50:43 UTC 2021.
checking for basename... /usr/bin/basename
checking for dirname... /usr/bin/dirname
checking for file... /usr/bin/file
checking for ldd... no
checking for bash... /bin/bash
checking for cat... /bin/cat
checking for chmod... /bin/chmod
checking for cp... /bin/cp
checking for cut... /usr/bin/cut
checking for date... /bin/date
checking for gdiff... [not found]
checking for diff... /usr/bin/diff
checking for echo... echo [builtin]
checking for expr... /usr/bin/expr
checking for find... /usr/bin/find
checking for gunzip... /bin/gunzip
checking for pigz... [not found]
checking for gzip... /bin/gzip
checking for head... /usr/bin/head
checking for ln... /bin/ln
checking for ls... /bin/ls
checking for gmkdir... [not found]
checking for mkdir... /bin/mkdir
checking for mktemp... /bin/mktemp
checking for mv... /bin/mv
checking for gawk... /usr/bin/gawk
checking for printf... printf [builtin]
checking for rm... /bin/rm
checking for rmdir... /bin/rmdir
checking for sh... /bin/sh
checking for sort... /usr/bin/sort
checking for tail... /usr/bin/tail
checking for gtar... /bin/gtar
checking for tee... /usr/bin/tee
checking for touch... /bin/touch
checking for tr... /usr/bin/tr
checking for uname... /bin/uname
checking for wc... /usr/bin/wc
checking for xargs... /usr/bin/xargs
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for a sed that does not truncate output... /bin/sed
checking for df... /bin/df
checking for nice... /bin/nice
checking for greadlink... [not found]
checking for readlink... /usr/bin/readlink
checking for cygpath... [not found]
checking for wslpath... [not found]
checking for lsb_release... [not found]
checking for cmd.exe... [not found]
checking for cmp... /usr/bin/cmp
checking for uniq... /usr/bin/uniq
checking build system type... riscv64-unknown-linux-gnu
checking host system type... riscv64-unknown-linux-gnu
checking target system type... riscv64-unknown-linux-gnu
checking openjdk-build os-cpu... linux-riscv64
checking openjdk-build C library... gnu
checking openjdk-target os-cpu... linux-riscv64
checking openjdk-target C library... gnu
checking compilation type... native
checking for top-level directory... /home/root/abhi/jdk
checking if custom source is suppressed (openjdk-only)... disabled, default
checking for --enable-debug... disabled, default
checking which debug level to use... release
checking which variants of the JVM to build... server
checking if absolute paths should be allowed in the build output... no, release build
checking for sysroot...
checking for toolchain path...
checking for extra path...
checking where to store configuration... in default location
checking what configuration name to use... linux-riscv64-server-release
checking for zypper... [not found]
checking for apt-get... /usr/bin/apt-get
checking for pandoc... [not found]
checking for gmake... [not found]
checking for make... /usr/bin/make
configure: Testing potential make at /usr/bin/make, found using make in PATH
configure: Using GNU make at /usr/bin/make (version: GNU Make 4.3)
checking if make --output-sync is supported... yes
checking for output-sync value... none
checking if find supports -delete... yes
checking what type of tar was found... gnu
checking that grep (/bin/grep) -Fx handles empty lines in the pattern list correctly... yes
checking for unzip... /usr/bin/unzip
checking for zip... /usr/bin/zip
checking for greadelf... [not found]
checking for readelf... /usr/bin/readelf
checking for dot... [not found]
checking for hg... [not found]
checking for git... /usr/bin/git
checking for stat... /bin/stat
checking for time... time [builtin]
checking for flock... /usr/bin/flock
checking for dtrace... [not found]
checking for gpatch... [not found]
checking for patch... /usr/bin/patch
checking for ulimit... ulimit [builtin]
checking bash version... 5.0.18
checking if bash supports pipefail... yes
checking if bash supports errexit (-e)... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for default LOG value...
checking if packaged modules are kept... enabled, default
checking for version string... 18-internal+0-adhoc.root.jdk
checking for javac... [not found]
checking for java... [not found]
configure: Could not find a valid Boot JDK. OpenJDK distributions are available at http://jdk.java.net/.
configure: This might be fixed by explicitly setting --with-boot-jdk
configure: error: Cannot continue
configure exiting with result code 1
root@exaleapsemi-3:~/abhi/jdk# apt-get install libcups2-dev
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package libcups2-dev
root@exaleapsemi-3:~/abhi/jdk# apt-get install libfontconfig1-dev
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package libfontconfig1-dev
root@exaleapsemi-3:~/abhi/jdk# apt-get install libasound2-dev
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package libasound2-dev
root@exaleapsemi-3:~/abhi/jdk# bash configure
configure: Configuration created at Thu Aug 26 08:52:37 UTC 2021.
checking for basename... /usr/bin/basename
checking for dirname... /usr/bin/dirname
checking for file... /usr/bin/file
checking for ldd... no
checking for bash... /bin/bash
checking for cat... /bin/cat
checking for chmod... /bin/chmod
checking for cp... /bin/cp
checking for cut... /usr/bin/cut
checking for date... /bin/date
checking for gdiff... [not found]
checking for diff... /usr/bin/diff
checking for echo... echo [builtin]
checking for expr... /usr/bin/expr
checking for find... /usr/bin/find
checking for gunzip... /bin/gunzip
checking for pigz... [not found]
checking for gzip... /bin/gzip
checking for head... /usr/bin/head
checking for ln... /bin/ln
checking for ls... /bin/ls
checking for gmkdir... [not found]
checking for mkdir... /bin/mkdir
checking for mktemp... /bin/mktemp
checking for mv... /bin/mv
checking for gawk... /usr/bin/gawk
checking for printf... printf [builtin]
checking for rm... /bin/rm
checking for rmdir... /bin/rmdir
checking for sh... /bin/sh
checking for sort... /usr/bin/sort
checking for tail... /usr/bin/tail
checking for gtar... /bin/gtar
checking for tee... /usr/bin/tee
checking for touch... /bin/touch
checking for tr... /usr/bin/tr
checking for uname... /bin/uname
checking for wc... /usr/bin/wc
checking for xargs... /usr/bin/xargs
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for a sed that does not truncate output... /bin/sed
checking for df... /bin/df
checking for nice... /bin/nice
checking for greadlink... [not found]
checking for readlink... /usr/bin/readlink
checking for cygpath... [not found]
checking for wslpath... [not found]
checking for lsb_release... [not found]
checking for cmd.exe... [not found]
checking for cmp... /usr/bin/cmp
checking for uniq... /usr/bin/uniq
checking build system type... riscv64-unknown-linux-gnu
checking host system type... riscv64-unknown-linux-gnu
checking target system type... riscv64-unknown-linux-gnu
checking openjdk-build os-cpu... linux-riscv64
checking openjdk-build C library... gnu
checking openjdk-target os-cpu... linux-riscv64
checking openjdk-target C library... gnu
checking compilation type... native
checking for top-level directory... /home/root/abhi/jdk
checking if custom source is suppressed (openjdk-only)... disabled, default
checking for --enable-debug... disabled, default
checking which debug level to use... release
checking which variants of the JVM to build... server
checking if absolute paths should be allowed in the build output... no, release build
checking for sysroot...
checking for toolchain path...
checking for extra path...
checking where to store configuration... in default location
checking what configuration name to use... linux-riscv64-server-release
checking for zypper... [not found]
checking for apt-get... /usr/bin/apt-get
checking for pandoc... [not found]
checking for gmake... [not found]
checking for make... /usr/bin/make
configure: Testing potential make at /usr/bin/make, found using make in PATH
configure: Using GNU make at /usr/bin/make (version: GNU Make 4.3)
checking if make --output-sync is supported... yes
checking for output-sync value... none
checking if find supports -delete... yes
checking what type of tar was found... gnu
checking that grep (/bin/grep) -Fx handles empty lines in the pattern list correctly... yes
checking for unzip... /usr/bin/unzip
checking for zip... /usr/bin/zip
checking for greadelf... [not found]
checking for readelf... /usr/bin/readelf
checking for dot... [not found]
checking for hg... [not found]
checking for git... /usr/bin/git
checking for stat... /bin/stat
checking for time... time [builtin]
checking for flock... /usr/bin/flock
checking for dtrace... [not found]
checking for gpatch... [not found]
checking for patch... /usr/bin/patch
checking for ulimit... ulimit [builtin]
checking bash version... 5.0.18
checking if bash supports pipefail... yes
checking if bash supports errexit (-e)... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for default LOG value...
checking if packaged modules are kept... enabled, default
checking for version string... 18-internal+0-adhoc.root.jdk
checking for javac... [not found]
checking for java... [not found]
configure: Could not find a valid Boot JDK. OpenJDK distributions are available at http://jdk.java.net/.
configure: This might be fixed by explicitly setting --with-boot-jdk
configure: error: Cannot continue
configure exiting with result code 1


Issue baking a new layer for a custom kernel #kernel

nagesh shamnur <nagesh.shamnur@...>
 

Hi Group,
   I am trying to add a new layer for a custom RTOS which supports RISCV32 architecture. When i run bitbake i bumped into following error:
"
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb: QA Issue: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb: Variable RDEPENDS is set as not being package specific, please fix this. [pkgvarcheck]
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb: QA Issue: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb: Variable RRECOMMENDS is set as not being package specific, please fix this. [pkgvarcheck]
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb: Fatal QA errors found, failing task.
ERROR: Failed to parse recipe: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb
WARNING: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-yappi_1.0.bb: Cooker received SIGTERM, shutting down...
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-werkzeug_1.0.0.bb: QA Issue: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-werkzeug_1.0.0.bb: Variable RDEPENDS is set as not being package specific, please fix this. [pkgvarcheck]
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-werkzeug_1.0.0.bb: QA Issue: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-werkzeug_1.0.0.bb: Variable RRECOMMENDS is set as not being package specific, please fix this. [pkgvarcheck]
ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-werkzeug_1.0.0.bb: Fatal QA errors found, failing task.
WARNING: Cooker received SIGTERM, shutting down...
WARNING: /home/gitee-ohos/ohos/AllScenariosOS/sources/poky/../meta-openembedded/meta-python/recipes-devtools/python/python3-zipp_0.6.0.bb: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...
WARNING: Cooker received SIGTERM, shutting down...

Summary: There were 12 WARNING messages shown.
Summary: There were 7 ERROR messages shown, returning a non-zero exit code.
"

Looking for the exact line which might have created a problem, found out that the issue is happening in the following line
"PACKAGES =. "${PN}-test " from the file ./meta-openembedded/meta-python/recipes-devtools/python/python3-zopeinterface_4.7.1.bb.

i have tried the following options, but none of them have helped in solving the issue.
1) I suspected that missing python3native might have resulted in the problem and included "inherit python3native" in my recipe file,
2) Also checked for presence of RDEPENDS in my recipe file as below: "LAYERDEPENDS_xxx ="core meta-python"

Please suggest a way out of this issue.

Thanks!


[meta-security][PATCH] dm-verity-img.bbclass: Expose --data-block-size for configuration

Paulo Neves
 

From: Christer Fletcher <christer.fletcher@...>

Add DM_VERITY_IMAGE_DATA_BLOCK_SIZE to be able to set the
--data-block-size used in veritysetup. Tuning this value effects the
performance and size of the resulting image.

Signed-off-by: Christer Fletcher <christer.fletcher@...>
Signed-off-by: Paulo Neves <paulo.neves1@...>
---
classes/dm-verity-img.bbclass | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/classes/dm-verity-img.bbclass b/classes/dm-verity-img.bbclass
index 16d395b..b311fc5 100644
--- a/classes/dm-verity-img.bbclass
+++ b/classes/dm-verity-img.bbclass
@@ -22,6 +22,9 @@
# is stored where it can be installed into associated initramfs rootfs.
STAGING_VERITY_DIR ?= "${TMPDIR}/work-shared/${MACHINE}/dm-verity"

+# Define the data block size to use in veritysetup.
+DM_VERITY_IMAGE_DATA_BLOCK_SIZE ?= "1024"
+
# Process the output from veritysetup and generate the corresponding .env
# file. The output from veritysetup is not very machine-friendly so we need to
# convert it to some better format. Let's drop the first line (doesn't contain
@@ -57,7 +60,7 @@ verity_setup() {

# Let's drop the first line of output (doesn't contain any useful info)
# and feed the rest to another function.
- veritysetup --data-block-size=1024 --hash-offset=$SIZE format $OUTPUT $OUTPUT | tail -n +2 | process_verity
+ veritysetup --data-block-size=${DM_VERITY_IMAGE_DATA_BLOCK_SIZE} --hash-offset=$SIZE format $OUTPUT $OUTPUT | tail -n +2 | process_verity
}

VERITY_TYPES = "ext2.verity ext3.verity ext4.verity btrfs.verity"
--
2.25.1


Re: gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool?

Peter Bergin
 

Hi Matthias,

On 2021-09-01 12:33, Matthias Klein wrote:
Hello,

is it somehow possible to add the ubxtool in the gpsd-utils package?

(I use the current master branch)
gpsd recipe is located in meta-oe. As the ubxtool file is present in the build it is possible to add it. Just make sure it is installed in the do_install step and then that the file is added to FILES_gps-utils variable.

Best regards,
/Peter


Re: gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool?

Zoran
 

To add every package (into poky) by every personal wish of any Yocto
user, or not to add any package without exclusion, that is the
question?

Why not to do addition of the proprietary layer for missing package or
group of missing by the same/similar context packages???

Zee
_______

On Wed, Sep 1, 2021 at 12:33 PM Matthias Klein
<matthias.klein@...> wrote:

Hello,

is it somehow possible to add the ubxtool in the gpsd-utils package?

(I use the current master branch)

Best regards,
Matthias




gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool?

Matthias Klein
 

Hello,

is it somehow possible to add the ubxtool in the gpsd-utils package?

(I use the current master branch)

Best regards,
Matthias


Re: editing Makefile after configure stage to disable -Werror

Khem Raj
 

On 8/31/21 12:52 AM, Ivan Riabtsov wrote:
i cleaned out -Werror wherever possible with command:
sed -i 's/-Werror//g' $(find . -type f -exec egrep -l _no_Werror {} \;)
and elfutils is builded
Please try backporting this fix

https://sourceware.org/git/?p=elfutils.git;a=commit;h=a01938d584b91e747167bb4b3f30ec300c4d6e43

if this is not enough then I think you just need to edit config/eu.am to remove -Werror and perhaps thats enough, but upstream elfutils is generally receptive to
Werror issues, so I would also suggest that in parallel you report it
upstream as well.

вт, 31 авг. 2021 г. в 09:41, Ivan Riabtsov via lists.yoctoproject.org
<ivriabtsov=gmail.com@...>:

Hello, I have the following error:

../../elfutils-0.166/libelf/libelfP.h:53:30: error: ‘__elf64_msize’
specifies less restrictive attribute than its target ‘elf64_fsize’:
‘const’ [-Werror=missing-attributes]

i try to solve this by patch:

diff -Naur elfutils-0.166_orig/libelf/libelfP.h elfutils-0.166/libelf/libelfP.h
--- elfutils-0.166_orig/libelf/libelfP.h 2016-01-12 15:49:19.000000000 +0300
+++ elfutils-0.166/libelf/libelfP.h 2021-08-30 19:38:44.866175082 +0300
@@ -48,6 +48,8 @@


/* Helper Macros to write 32 bit and 64 bit functions. */
+#pragma GCC diagnostic push
+#pragma GCC diagnostic ignored "-Wmissing-attributes"
#define __elfw2_(Bits, Name) __elf##Bits##_##Name
#define elfw2_(Bits, Name) elf##Bits##_##Name
#define ElfW2_(Bits, Name) Elf##Bits##_##Name
@@ -632,4 +634,5 @@
#define INVALID_NDX(ndx, type, data) \
unlikely ((data)->d_size / sizeof (type) <= (unsigned int) (ndx))

+#pragma GCC diagnostic pop
#endif /* libelfP.h */


But the patch does not work, error appears again.


i try to add --disable-werror to configure flags, but i have follows warning:

configure: WARNING: unrecognized options: --disable-werror.


The only solution to the problem I could think of is editing the
Makefile after configuration, please tell me how this can be done?






Re: Binary compliance validation

Anatol Belski
 

Hi,

On 8/31/2021 5:58 PM, Bruce Ashfield wrote:
On Tue, Aug 31, 2021 at 11:48 AM Anatol Belski
<anbelski@...> wrote:
Hi,

I'm writing to present an ABI compliance check mechanism for Poky
recently developed to help improve the product stability. It is still
an early work which however has already proven itself useful and thus
the time seems right to ask for the community view.

Binary compliance is an important metric, when a distrubition intends
to provide stability guarantees to consumers outside the monolithic
image build. For example, projects utilizing the SDK might not be in
sync with the image builds from even the same branch. Even in stable
branches where bugfixes, security patches or even non breaching
upgrades have to flow in as necessary, there's is currently no
verifiable mechainsm to ensure the binary compatibility long term.

The currently implemented validation is based on libabigail and as such
is focused on the ABI compliance. Libabigail is a tool developed by Red
Hat and is in use for Fedora and RHEL RPM builds. Some companies are
known to utilize libabigail to support the kernel maintanance (Linux
kernel for Android). The meta layer contains a bbclass extending the
buildhistory functionality with the ABI serialization and comparison.
One buildhistory version taken as a baseline would serve the comparison
with any follow up builds. The ABI changes detected are then reported.

The handling routines in Poky are currently attached to the install
task, which implies the baseline build needs to take place with the
sstate disabled. The follow up buids can use sstate and in that case
the postinstall routines will be invoked only if some change took place
and thus do_install has been called.

The implementation is made as a core Python module, which can be used
in a Yocto layer or imported in any other script. The layer is
available under:
https://github.com/clio-project/meta-binaryaudit

and the accompanying python module (which moves at some faster pace and
is synchronized into the layer) and a command line tool:
https://github.com/clio-project/python-binaryaudit

The layer is yet an early work and the impluementation doesn't exhaust
all the possible features of Poky and libabigail. However, it already
proves itself helpful and is used for some real products to esure the
ABI stability. Certainly the mechanisms and the integration can be
improved.

The future for this layer is open containing at least the topics below:

- Binary size auditing.
- Security auditing.

As a shorter term serviceableness, the ABI compliance validation
mechanism seems to be a useful tool in helping to keep promises on LTS,
but would most likely also help maintaining non LTS branches. It would
be great to receive any feedback, reviews and ideas in regard to meta-
binaryaudit.
Out of curiosity, are you coordinating with the work sent in March by BMW ?

see the email with the subject: [yocto] Demo of abi checker hook with hashequiv

And the associated layers: https://github.com/bmwcarit/meta-abicompat
and https://github.com/bmwcarit/meta-abicompat-poky

Thanks for the pointer! Nope, there's no coordination, it's a separate effort and seems the approach and goals are somewhat different. The sstate handling is however a very interesting approach. One could check if these works can be merged together, if there's an interest.

Regards

Anatol

Bruce

Thanks!

Anatol





--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II




Re: Binary compliance validation

Bruce Ashfield
 

On Tue, Aug 31, 2021 at 11:48 AM Anatol Belski
<anbelski@...> wrote:

Hi,

I'm writing to present an ABI compliance check mechanism for Poky
recently developed to help improve the product stability. It is still
an early work which however has already proven itself useful and thus
the time seems right to ask for the community view.

Binary compliance is an important metric, when a distrubition intends
to provide stability guarantees to consumers outside the monolithic
image build. For example, projects utilizing the SDK might not be in
sync with the image builds from even the same branch. Even in stable
branches where bugfixes, security patches or even non breaching
upgrades have to flow in as necessary, there's is currently no
verifiable mechainsm to ensure the binary compatibility long term.

The currently implemented validation is based on libabigail and as such
is focused on the ABI compliance. Libabigail is a tool developed by Red
Hat and is in use for Fedora and RHEL RPM builds. Some companies are
known to utilize libabigail to support the kernel maintanance (Linux
kernel for Android). The meta layer contains a bbclass extending the
buildhistory functionality with the ABI serialization and comparison.
One buildhistory version taken as a baseline would serve the comparison
with any follow up builds. The ABI changes detected are then reported.

The handling routines in Poky are currently attached to the install
task, which implies the baseline build needs to take place with the
sstate disabled. The follow up buids can use sstate and in that case
the postinstall routines will be invoked only if some change took place
and thus do_install has been called.

The implementation is made as a core Python module, which can be used
in a Yocto layer or imported in any other script. The layer is
available under:
https://github.com/clio-project/meta-binaryaudit

and the accompanying python module (which moves at some faster pace and
is synchronized into the layer) and a command line tool:
https://github.com/clio-project/python-binaryaudit

The layer is yet an early work and the impluementation doesn't exhaust
all the possible features of Poky and libabigail. However, it already
proves itself helpful and is used for some real products to esure the
ABI stability. Certainly the mechanisms and the integration can be
improved.

The future for this layer is open containing at least the topics below:

- Binary size auditing.
- Security auditing.

As a shorter term serviceableness, the ABI compliance validation
mechanism seems to be a useful tool in helping to keep promises on LTS,
but would most likely also help maintaining non LTS branches. It would
be great to receive any feedback, reviews and ideas in regard to meta-
binaryaudit.
Out of curiosity, are you coordinating with the work sent in March by BMW ?

see the email with the subject: [yocto] Demo of abi checker hook with hashequiv

And the associated layers: https://github.com/bmwcarit/meta-abicompat
and https://github.com/bmwcarit/meta-abicompat-poky

Bruce


Thanks!

Anatol




--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


Binary compliance validation

Anatol Belski
 

Hi,

I'm writing to present an ABI compliance check mechanism for Poky
recently developed to help improve the product stability. It is still
an early work which however has already proven itself useful and thus
the time seems right to ask for the community view.

Binary compliance is an important metric, when a distrubition intends
to provide stability guarantees to consumers outside the monolithic
image build. For example, projects utilizing the SDK might not be in
sync with the image builds from even the same branch. Even in stable
branches where bugfixes, security patches or even non breaching
upgrades have to flow in as necessary, there's is currently no
verifiable mechainsm to ensure the binary compatibility long term.

The currently implemented validation is based on libabigail and as such
is focused on the ABI compliance. Libabigail is a tool developed by Red
Hat and is in use for Fedora and RHEL RPM builds. Some companies are
known to utilize libabigail to support the kernel maintanance (Linux
kernel for Android). The meta layer contains a bbclass extending the
buildhistory functionality with the ABI serialization and comparison.
One buildhistory version taken as a baseline would serve the comparison
with any follow up builds. The ABI changes detected are then reported.

The handling routines in Poky are currently attached to the install
task, which implies the baseline build needs to take place with the
sstate disabled. The follow up buids can use sstate and in that case
the postinstall routines will be invoked only if some change took place
and thus do_install has been called.

The implementation is made as a core Python module, which can be used
in a Yocto layer or imported in any other script. The layer is
available under:
https://github.com/clio-project/meta-binaryaudit

and the accompanying python module (which moves at some faster pace and
is synchronized into the layer) and a command line tool:
https://github.com/clio-project/python-binaryaudit

The layer is yet an early work and the impluementation doesn't exhaust
all the possible features of Poky and libabigail. However, it already
proves itself helpful and is used for some real products to esure the
ABI stability. Certainly the mechanisms and the integration can be
improved.

The future for this layer is open containing at least the topics below:

- Binary size auditing.
- Security auditing.

As a shorter term serviceableness, the ABI compliance validation
mechanism seems to be a useful tool in helping to keep promises on LTS,
but would most likely also help maintaining non LTS branches. It would
be great to receive any feedback, reviews and ideas in regard to meta-
binaryaudit.

Thanks!

Anatol


Yocto Project Status WW35`21

Stephen Jolley
 

Current Dev Position: YP 3.4 M3 (Feature Freeze)

Next Deadline: 23rd Aug. 2021 YP 3.4 M3 build (Feature Freeze)

 

Next Team Meetings:

 

Key Status/Updates:

  • We are now at feature freeze for YP 3.4
  • Rust was merged into core, it was touch and go whether we could/would or not. Unfortunately there was an error found after merging with cargo-native on centos7 hosts which we still need to resolve before building M3.
  • Fixes for glibc 2.34 and pseudo were merged however this uses a binary shim and isn’t an ideal way to solve the issues. We need to find a way to have active development on pseudo with investigation into possible replacement approaches.
  • A kernel issue introduced in recent kernel module versioning changes needs to resolved before we can build M3.
  • The glibc 2.34 upgrade caused issues with docker and the clone3 syscall returning EPERM instead of ENOSYS. We will likely have to add a workaround to our glibc until released versions of docker have the upstream fix.
  • Intermittent issues are ongoing and help is very much welcome on these issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

 

Ways to contribute:

 

YP 3.4 Milestone Dates:

  • YP 3.4 M3 build date 2021/08/23 (Feature Freeze)
  • YP 3.4 M3 Release date 2021/09/03
  • YP 3.4 M4 build date 2021/10/04
  • YP 3.4 M4 Release date 2021/10/29

 

Planned upcoming dot releases:

  • YP 3.1.11 build date 2021/09/13
  • YP 3.1.11 release date 2021/9/24

 

Tracking Metrics:

 

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: extrausers-bbclass: plaintext password (since shadow update to 4.9)

Matthias Klein
 

Hello Peter,

thanks for the solution!

Many greetings,
Matthias

-----Ursprüngliche Nachricht-----
Von: Peter Bergin <peter@...>
Gesendet: Dienstag, 31. August 2021 09:45
An: Matthias Klein <matthias.klein@...>; yocto@...
Betreff: Re: [yocto] extrausers-bbclass: plaintext password (since shadow update to 4.9)

Hi Matthias,

On 2021-08-31 09:03, Matthias Klein wrote:
But I have not found a way to set the password with EXTRA_USERS_PARAMS.
Do you know a working variant?
Is it a requirement that you need to regenerate the hash on every build?
If not one solution can be:

    inherit extrausers

    #
    # HASH generated with this command:
    # python3 -c "import crypt; print(crypt.crypt('toor', crypt.METHOD_SHA512))"
    #
    HASH =
"\\\$6\\\$8Z5vMcqCIB19PgY8\\\$Sv4kAfsH1k.SANHL5JVb6hdqmQWHOeH0Rjrjyii7fGAK20Gclj/.qiBvUPnAfh.WSsr1.XV0pUNom2L9oYYDV/"

    EXTRA_USERS_PARAMS = " \
       usermod -p ${HASH} root; \
    "

Best regards,
/Peter


Re: editing Makefile after configure stage to disable -Werror

Markus Volk
 

you could try to add a line like this to your recipe:

CFLAGS:append = " -Wno-error=missing-attributes"


Am 31.08.21 um 08:41 schrieb Ivan Riabtsov:

Hello, I have the following error:

../../elfutils-0.166/libelf/libelfP.h:53:30: error: ‘__elf64_msize’
specifies less restrictive attribute than its target ‘elf64_fsize’:
‘const’ [-Werror=missing-attributes]

i try to solve this by patch:

diff -Naur elfutils-0.166_orig/libelf/libelfP.h elfutils-0.166/libelf/libelfP.h
--- elfutils-0.166_orig/libelf/libelfP.h 2016-01-12 15:49:19.000000000 +0300
+++ elfutils-0.166/libelf/libelfP.h 2021-08-30 19:38:44.866175082 +0300
@@ -48,6 +48,8 @@


 /* Helper Macros to write 32 bit and 64 bit functions.  */
+#pragma GCC diagnostic push
+#pragma GCC diagnostic ignored "-Wmissing-attributes"
 #define __elfw2_(Bits, Name) __elf##Bits##_##Name
 #define elfw2_(Bits, Name) elf##Bits##_##Name
 #define ElfW2_(Bits, Name) Elf##Bits##_##Name
@@ -632,4 +634,5 @@
 #define INVALID_NDX(ndx, type, data) \
   unlikely ((data)->d_size / sizeof (type) <= (unsigned int) (ndx))

+#pragma GCC diagnostic pop
 #endif  /* libelfP.h */


But the patch does  not work, error appears again.


i try to add --disable-werror to configure flags, but i have follows warning:

configure: WARNING: unrecognized options: --disable-werror.


The only solution to the problem I could think of is editing the
Makefile after configuration, please tell me how this can be done?




Re: downgrade openssl libraryes

Bas Mevissen
 

On 2021-08-30 16:56, Ivan Riabtsov wrote:
I have phytec imx6ul board with a preinstalled os. On this os opessl
version is 1.0.2j i need to build nginx for this board, but i can't
build yocto same version as i have on board, so I grabbed a newer
version of yocto from phytec site, rolled back glibc and try to roll
back openssl. I do not want to flash the device, as I'm afraid to get
brick
Why are you afraid to brick the device? You can use mfgtool to reflash the device from scratch, including u-boot. It works with a special boot mode pin setting and uses an USB port. Depending on the board, one might need to buy or create a custom cable.

Bas.

пн, 30 авг. 2021 г. в 16:51, Alexander Kanavin <alex.kanavin@...>:
openssl 1.0.2 went out of support at the end of 2019 and you should not be using it. What is the problem you need to solve?
Alex
On Mon, 30 Aug 2021 at 15:33, Ivan Riabtsov <ivriabtsov@...> wrote:
hello i am trying to rollback openssl version from 1.1.1i to 1.0.2j.
Copied the recipe openssl_1.1.1i.bb to openssl_1.0.2j.bb, saved the
openssl_1.1.1i.bb version with the name openssl_1.1.1i.bb.backup
Отредактировал новый файл, вот разница в файлах:
diff -Nau ./openssl_1.1.1i.bb.backup ./openssl_1.0.2j.bb
--- ./openssl_1.1.1i.bb.backup 2021-08-27 14:46:07.085808702 +0300
+++ ./openssl_1.0.2j.bb 2021-08-27 16:12:14.216430734 +0300
@@ -7,23 +7,19 @@
# "openssl" here actually means both OpenSSL and SSLeay licenses apply
# (see meta/files/common-licenses/OpenSSL to which "openssl" is
SPDXLICENSEMAPped)
LICENSE = "openssl"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=d343e62fc9c833710bbbed25f27364c8"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=27ffa5d74bb5a337056c14b2ef93fbf6"
DEPENDS = "hostperl-runtime-native"
SRC_URI = "http://www.openssl.org/source/openssl-${PV}.tar.gz \
file://run-ptest \
- file://0001-skip-test_symbol_presence.patch \
- file://0001-buildinfo-strip-sysroot-and-debug-prefix-map-from-co.patch
\
- file://afalg.patch \
- file://reproducible.patch \
"
SRC_URI_append_class-nativesdk = " \
file://environment.d-openssl.sh \
"
-SRC_URI[sha256sum] =
"e8be6a35fe41d10603c3cc635e93289ed00bf34b79671a3a4de64fcee00d5242"
+SRC_URI[sha256sum] =
"e7aff292be21c259c6af26469c7a9b3ba26e9abaaffd325e3dccc9785256c431"
inherit lib_package multilib_header multilib_script ptest
MULTILIB_SCRIPTS = "${PN}-bin:${bindir}/c_rehash"
@@ -122,7 +118,7 @@
# WARNING: do not set compiler/linker flags (-I/-D etc.) in
EXTRA_OECONF, as they will fully replace the
# environment variables set by bitbake. Adjust the environment
variables instead.
HASHBANGPERL="/usr/bin/env perl" PERL=perl
PERL5LIB="${S}/external/perl/Text-Template-1.46/lib/" \
- perl ${S}/Configure ${EXTRA_OECONF} ${PACKAGECONFIG_CONFARGS}
--prefix=$useprefix --openssldir=${libdir}/ssl-1.1 --libdir=${libdir}
$target
+ perl ${S}/Configure ${EXTRA_OECONF} ${PACKAGECONFIG_CONFARGS}
--prefix=$useprefix --openssldir=${libdir}/ssl-1.0 --libdir=${libdir}
$target
perl ${B}/configdata.pm --dump
}
@@ -134,30 +130,30 @@
# Create SSL structure for packages such as ca-certificates which
# contain hard-coded paths to /etc/ssl. Debian does the same.
install -d ${D}${sysconfdir}/ssl
- mv ${D}${libdir}/ssl-1.1/certs \
- ${D}${libdir}/ssl-1.1/private \
- ${D}${libdir}/ssl-1.1/openssl.cnf \
+ mv ${D}${libdir}/ssl-1.0/certs \
+ ${D}${libdir}/ssl-1.0/private \
+ ${D}${libdir}/ssl-1.0/openssl.cnf \
${D}${sysconfdir}/ssl/
# Although absolute symlinks would be OK for the target, they become
# invalid if native or nativesdk are relocated from sstate.
- ln -sf ${@oe.path.relative('${libdir}/ssl-1.1',
'${sysconfdir}/ssl/certs')} ${D}${libdir}/ssl-1.1/certs
- ln -sf ${@oe.path.relative('${libdir}/ssl-1.1',
'${sysconfdir}/ssl/private')} ${D}${libdir}/ssl-1.1/private
- ln -sf ${@oe.path.relative('${libdir}/ssl-1.1',
'${sysconfdir}/ssl/openssl.cnf')} ${D}${libdir}/ssl-1.1/openssl.cnf
+ ln -sf ${@oe.path.relative('${libdir}/ssl-1.0',
'${sysconfdir}/ssl/certs')} ${D}${libdir}/ssl-1.0/certs
+ ln -sf ${@oe.path.relative('${libdir}/ssl-1.0',
'${sysconfdir}/ssl/private')} ${D}${libdir}/ssl-1.0/private
+ ln -sf ${@oe.path.relative('${libdir}/ssl-1.0',
'${sysconfdir}/ssl/openssl.cnf')} ${D}${libdir}/ssl-1.0/openssl.cnf
}
do_install_append_class-native () {
create_wrapper ${D}${bindir}/openssl \
- OPENSSL_CONF=${libdir}/ssl-1.1/openssl.cnf \
- SSL_CERT_DIR=${libdir}/ssl-1.1/certs \
- SSL_CERT_FILE=${libdir}/ssl-1.1/cert.pem \
- OPENSSL_ENGINES=${libdir}/engines-1.1
+ OPENSSL_CONF=${libdir}/ssl-1.0/openssl.cnf \
+ SSL_CERT_DIR=${libdir}/ssl-1.0/certs \
+ SSL_CERT_FILE=${libdir}/ssl-1.0/cert.pem \
+ OPENSSL_ENGINES=${libdir}/engines-1.0
}
do_install_append_class-nativesdk () {
mkdir -p ${D}${SDKPATHNATIVE}/environment-setup.d
install -m 644 ${WORKDIR}/environment.d-openssl.sh
${D}${SDKPATHNATIVE}/environment-setup.d/openssl.sh
- sed 's|/usr/lib/ssl/|/usr/lib/ssl-1.1/|g' -i
${D}${SDKPATHNATIVE}/environment-setup.d/openssl.sh
+ sed 's|/usr/lib/ssl/|/usr/lib/ssl-1.0/|g' -i
${D}${SDKPATHNATIVE}/environment-setup.d/openssl.sh
}
PTEST_BUILD_HOST_FILES += "configdata.pm"
@@ -170,8 +166,8 @@
cp -r ${S}/external ${B}/test ${S}/test ${B}/fuzz ${S}/util
${B}/util ${D}${PTEST_PATH}
# For test_shlibload
- ln -s ${libdir}/libcrypto.so.1.1 ${D}${PTEST_PATH}/
- ln -s ${libdir}/libssl.so.1.1 ${D}${PTEST_PATH}/
+ ln -s ${libdir}/libcrypto.so.1.0 ${D}${PTEST_PATH}/
+ ln -s ${libdir}/libssl.so.1.0 ${D}${PTEST_PATH}/
install -d ${D}${PTEST_PATH}/apps
ln -s ${bindir}/openssl ${D}${PTEST_PATH}/apps
@@ -192,11 +188,11 @@
FILES_libcrypto = "${libdir}/libcrypto${SOLIBS}"
FILES_libssl = "${libdir}/libssl${SOLIBS}"
FILES_openssl-conf = "${sysconfdir}/ssl/openssl.cnf \
- ${libdir}/ssl-1.1/openssl.cnf* \
+ ${libdir}/ssl-1.0/openssl.cnf* \
"
-FILES_${PN}-engines = "${libdir}/engines-1.1"
-FILES_${PN}-misc = "${libdir}/ssl-1.1/misc"
-FILES_${PN} =+ "${libdir}/ssl-1.1/*"
+FILES_${PN}-engines = "${libdir}/engines-1.0"
+FILES_${PN}-misc = "${libdir}/ssl-1.0/misc"
+FILES_${PN} =+ "${libdir}/ssl-1.0/*"
FILES_${PN}_append_class-nativesdk = "
${SDKPATHNATIVE}/environment-setup.d/openssl.sh"
CONFFILES_openssl-conf = "${sysconfdir}/ssl/openssl.cnf"
вот новый получившийся файл:
cat openssl_1.0.2j.bb
SUMMARY = "Secure Socket Layer"
DESCRIPTION = "Secure Socket Layer (SSL) binary and related
cryptographic tools."
HOMEPAGE = "http://www.openssl.org/"
BUGTRACKER = "http://www.openssl.org/news/vulnerabilities.html"
SECTION = "libs/network"
# "openssl" here actually means both OpenSSL and SSLeay licenses apply
# (see meta/files/common-licenses/OpenSSL to which "openssl" is
SPDXLICENSEMAPped)
LICENSE = "openssl"
LIC_FILES_CHKSUM = "file://LICENSE;md5=27ffa5d74bb5a337056c14b2ef93fbf6"
DEPENDS = "hostperl-runtime-native"
SRC_URI = "http://www.openssl.org/source/openssl-${PV}.tar.gz \
file://run-ptest \
"
SRC_URI_append_class-nativesdk = " \
file://environment.d-openssl.sh \
"
SRC_URI[sha256sum] =
"e7aff292be21c259c6af26469c7a9b3ba26e9abaaffd325e3dccc9785256c431"
inherit lib_package multilib_header multilib_script ptest
MULTILIB_SCRIPTS = "${PN}-bin:${bindir}/c_rehash"
PACKAGECONFIG ?= ""
PACKAGECONFIG_class-native = ""
PACKAGECONFIG_class-nativesdk = ""
PACKAGECONFIG[cryptodev-linux] =
"enable-devcryptoeng,disable-devcryptoeng,cryptodev-linux,,cryptodev-module"
B = "${WORKDIR}/build"
do_configure[cleandirs] = "${B}"
#| ./libcrypto.so: undefined reference to `getcontext'
#| ./libcrypto.so: undefined reference to `setcontext'
#| ./libcrypto.so: undefined reference to `makecontext'
EXTRA_OECONF_append_libc-musl = " no-async"
EXTRA_OECONF_append_libc-musl_powerpc64 = " no-asm"
# adding devrandom prevents openssl from using getrandom() which is
not available on older glibc versions
# (native versions can be built with newer glibc, but then relocated
onto a system with older glibc)
EXTRA_OECONF_class-native = "--with-rand-seed=os,devrandom"
EXTRA_OECONF_class-nativesdk = "--with-rand-seed=os,devrandom"
# Relying on hardcoded built-in paths causes openssl-native to not be
relocateable from sstate.
CFLAGS_append_class-native = " -DOPENSSLDIR=/not/builtin
-DENGINESDIR=/not/builtin"
CFLAGS_append_class-nativesdk = " -DOPENSSLDIR=/not/builtin
-DENGINESDIR=/not/builtin"
do_configure () {
os=${HOST_OS}
case $os in
linux-gnueabi |\
linux-gnuspe |\
linux-musleabi |\
linux-muslspe |\
linux-musl )
os=linux
;;
*)
;;
esac
target="$os-${HOST_ARCH}"
case $target in
linux-arm*)
target=linux-armv4
;;
linux-aarch64*)
target=linux-aarch64
;;
linux-i?86 | linux-viac3)
target=linux-x86
;;
linux-gnux32-x86_64 | linux-muslx32-x86_64 )
target=linux-x32
;;
linux-gnu64-x86_64)
target=linux-x86_64
;;
linux-mips | linux-mipsel)
# specifying TARGET_CC_ARCH prevents openssl from (incorrectly) adding
target architecture flags
target="linux-mips32 ${TARGET_CC_ARCH}"
;;
linux-gnun32-mips*)
target=linux-mips64
;;
linux-*-mips64 | linux-mips64 | linux-*-mips64el | linux-mips64el)
target=linux64-mips64
;;
linux-microblaze* | linux-nios2* | linux-sh3 | linux-sh4 | linux-arc*)
target=linux-generic32
;;
linux-powerpc)
target=linux-ppc
;;
linux-powerpc64)
target=linux-ppc64
;;
linux-powerpc64le)
target=linux-ppc64le
;;
linux-riscv32)
target=linux-generic32
;;
linux-riscv64)
target=linux-generic64
;;
linux-sparc | linux-supersparc)
target=linux-sparcv9
;;
esac
useprefix=${prefix}
if [ "x$useprefix" = "x" ]; then
useprefix=/
fi
# WARNING: do not set compiler/linker flags (-I/-D etc.) in
EXTRA_OECONF, as they will fully replace the
# environment variables set by bitbake. Adjust the environment
variables instead.
HASHBANGPERL="/usr/bin/env perl" PERL=perl
PERL5LIB="${S}/external/perl/Text-Template-1.46/lib/" \
perl ${S}/Configure ${EXTRA_OECONF} ${PACKAGECONFIG_CONFARGS}
--prefix=$useprefix --openssldir=${libdir}/ssl-1.0 --libdir=${libdir}
$target
perl ${B}/configdata.pm --dump
}
do_install () {
oe_runmake DESTDIR="${D}" MANDIR="${mandir}" MANSUFFIX=ssl install
oe_multilib_header openssl/opensslconf.h
# Create SSL structure for packages such as ca-certificates which
# contain hard-coded paths to /etc/ssl. Debian does the same.
install -d ${D}${sysconfdir}/ssl
mv ${D}${libdir}/ssl-1.0/certs \
${D}${libdir}/ssl-1.0/private \
${D}${libdir}/ssl-1.0/openssl.cnf \
${D}${sysconfdir}/ssl/
# Although absolute symlinks would be OK for the target, they become
# invalid if native or nativesdk are relocated from sstate.
ln -sf ${@oe.path.relative('${libdir}/ssl-1.0',
'${sysconfdir}/ssl/certs')} ${D}${libdir}/ssl-1.0/certs
ln -sf ${@oe.path.relative('${libdir}/ssl-1.0',
'${sysconfdir}/ssl/private')} ${D}${libdir}/ssl-1.0/private
ln -sf ${@oe.path.relative('${libdir}/ssl-1.0',
'${sysconfdir}/ssl/openssl.cnf')} ${D}${libdir}/ssl-1.0/openssl.cnf
}
do_install_append_class-native () {
create_wrapper ${D}${bindir}/openssl \
OPENSSL_CONF=${libdir}/ssl-1.0/openssl.cnf \
SSL_CERT_DIR=${libdir}/ssl-1.0/certs \
SSL_CERT_FILE=${libdir}/ssl-1.0/cert.pem \
OPENSSL_ENGINES=${libdir}/engines-1.0
}
do_install_append_class-nativesdk () {
mkdir -p ${D}${SDKPATHNATIVE}/environment-setup.d
install -m 644 ${WORKDIR}/environment.d-openssl.sh
${D}${SDKPATHNATIVE}/environment-setup.d/openssl.sh
sed 's|/usr/lib/ssl/|/usr/lib/ssl-1.0/|g' -i
${D}${SDKPATHNATIVE}/environment-setup.d/openssl.sh
}
PTEST_BUILD_HOST_FILES += "configdata.pm"
PTEST_BUILD_HOST_PATTERN = "perl_version ="
do_install_ptest () {
# Prune the build tree
rm -f ${B}/fuzz/*.* ${B}/test/*.*
cp ${S}/Configure ${B}/configdata.pm ${D}${PTEST_PATH}
cp -r ${S}/external ${B}/test ${S}/test ${B}/fuzz ${S}/util ${B}/util
${D}${PTEST_PATH}
# For test_shlibload
ln -s ${libdir}/libcrypto.so.1.0 ${D}${PTEST_PATH}/
ln -s ${libdir}/libssl.so.1.0 ${D}${PTEST_PATH}/
install -d ${D}${PTEST_PATH}/apps
ln -s ${bindir}/openssl ${D}${PTEST_PATH}/apps
install -m644 ${S}/apps/*.pem ${S}/apps/*.srl ${S}/apps/openssl.cnf
${D}${PTEST_PATH}/apps
install -m755 ${B}/apps/CA.pl ${D}${PTEST_PATH}/apps
install -d ${D}${PTEST_PATH}/engines
install -m755 ${B}/engines/ossltest.so ${D}${PTEST_PATH}/engines
}
# Add the openssl.cnf file to the openssl-conf package. Make the libcrypto
# package RRECOMMENDS on this package. This will enable the configuration
# file to be installed for both the openssl-bin package and the libcrypto
# package since the openssl-bin package depends on the libcrypto package.
PACKAGES =+ "libcrypto libssl openssl-conf ${PN}-engines ${PN}-misc"
FILES_libcrypto = "${libdir}/libcrypto${SOLIBS}"
FILES_libssl = "${libdir}/libssl${SOLIBS}"
FILES_openssl-conf = "${sysconfdir}/ssl/openssl.cnf \
${libdir}/ssl-1.0/openssl.cnf* \
"
FILES_${PN}-engines = "${libdir}/engines-1.0"
FILES_${PN}-misc = "${libdir}/ssl-1.0/misc"
FILES_${PN} =+ "${libdir}/ssl-1.0/*"
FILES_${PN}_append_class-nativesdk = "
${SDKPATHNATIVE}/environment-setup.d/openssl.sh"
CONFFILES_openssl-conf = "${sysconfdir}/ssl/openssl.cnf"
RRECOMMENDS_libcrypto += "openssl-conf"
RDEPENDS_${PN}-ptest += "openssl-bin perl perl-modules bash"
RDEPENDS_${PN}-bin += "openssl-conf"
BBCLASSEXTEND = "native nativesdk"
CVE_PRODUCT = "openssl:openssl"
# Only affects OpenSSL >= 1.1.1 in combination with Apache < 2.4.37
# Apache in meta-webserver is already recent enough
CVE_CHECK_WHITELIST += "CVE-2019-0190"
I understand that I need to figure out the configs yourself, but I get
this error when executing the
bitbake openssl-native
ERROR: Execution of
'/home/ivr/work/yocto_orig/build/tmp/work/x86_64-linux/openssl-native/1.0.2j-r0/temp/run.do_configure.1071458'
failed with exit code 2:
| unable to read opensslv.h:No such file or directory
| Configuring for linux-x86_64
| no-devcryptoeng [option] OPENSSL_NO_DEVCRYPTOENG (skip dir)
| no-ec_nistp_64_gcc_128 [default] OPENSSL_NO_EC_NISTP_64_GCC_128
(skip dir)
| no-gmp [default] OPENSSL_NO_GMP (skip dir)
| no-jpake [experimental] OPENSSL_NO_JPAKE (skip dir)
| no-krb5 [krb5-flavor not specified] OPENSSL_NO_KRB5
| no-libunbound [experimental] OPENSSL_NO_LIBUNBOUND (skip dir)
| no-md2 [default] OPENSSL_NO_MD2 (skip dir)
| no-rc5 [default] OPENSSL_NO_RC5 (skip dir)
| no-rfc3779 [default] OPENSSL_NO_RFC3779 (skip dir)
| no-sctp [default] OPENSSL_NO_SCTP (skip dir)
| no-shared [default]
| no-ssl-trace [default] OPENSSL_NO_SSL_TRACE (skip dir)
| no-ssl2 [default] OPENSSL_NO_SSL2 (skip dir)
| no-store [experimental] OPENSSL_NO_STORE (skip dir)
| no-unit-test [default] OPENSSL_NO_UNIT_TEST (skip dir)
| no-weak-ssl-ciphers [default] OPENSSL_NO_WEAK_SSL_CIPHERS (skip dir)
| no-zlib [default]
| no-zlib-dynamic [default]
| IsMK1MF=0
| WARNING: exit code 2 from a shell command.
|
As far as I can understand, the opensslv.h file is generated just at
the configuration stage, why does the configuration stage give an
error of the absence of this file?

2801 - 2820 of 57400