[ptxdist] Documentation: Pre-Built Toolchain installation on Ubuntu: minor glitches or outdated
Following the documentation about installation of an OSELAS.Toolchain from Pengutronix Debian Archive [1] on a (mostly) fresh Ubuntu 22.04 derived installation, I ran into some details. Don't know about stock Debian resp. apt-get instead of apt behaviour, but I assume the same applies. According to docs, added "/etc/apt/sources.list.d/pengutronix.list" as: deb https://debian.pengutronix.de/debian/ jammy main contrib non-free Result: # apt update [...] Get:11 https://debian.pengutronix.de/debian jammy InRelease [4.042 B] Err:11 https://debian.pengutronix.de/debian jammy InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 69E81E916B7A3E09 NO_PUBKEY 94F58BAD054406A9 Reading package lists... Done W: GPG error: https://debian.pengutronix.de/debian jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 69E81E916B7A3E09 NO_PUBKEY 94F58BAD054406A9 E: The repository 'https://debian.pengutronix.de/debian jammy InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. # apt install pengutronix-archive-keyring Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package pengutronix-archive-keyring Plausible, as list was not installed above, due to missing key. So I manually fetched and installed (dpkg -i) the keyring: https://debian.pengutronix.de/debian/pool/main/p/pengutronix-archive-keyring/pengutronix-archive-keyring_2023.01.09_all.deb Now, package list is downloaded and used, but with some annoyance about missing arch in repo: # apt update [...] Get:8 https://debian.pengutronix.de/debian jammy/main amd64 Packages [14,9 kB] [...] Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://debian.pengutronix.de/debian jammy InRelease' doesn't support architecture 'i386' N: Skipping acquire of configured file 'contrib/binary-i386/Packages' as repository 'https://debian.pengutronix.de/debian jammy InRelease' doesn't support architecture 'i386' N: Skipping acquire of configured file 'non-free/binary-i386/Packages' as repository 'https://debian.pengutronix.de/debian jammy InRelease' doesn't support architecture 'i386' Limited "/etc/apt/sources.list.d/pengutronix.list" accordingly, by adding "[arch=amd64]", so we now have: deb [arch=amd64] https://debian.pengutronix.de/debian/ jammy main contrib non-free Final result is a working setup, without any annoying warnings. Unfortunately, I'm busy setting up a customer VM, so I'll just throw in these pointers, instead of trying to find a suitable updated wording for the docs, sorry. Best regards, Andreas [1] https://www.ptxdist.org/doc/environment.html#add-the-pengutronix-debian-archive -- carpe noctem engineering Ingenieurbuero fuer Hard- & Software-Entwicklung Andreas Pretzsch Dipl.-Ing. (FH) Andreas PretzschTel. +49-(0)711-3908735-7 Tuebinger Strasse 63Fax: +49-(0)711-3908735-9 70178 Stuttgart, Germanyemail: a...@cn-eng.de
[ptxdist] arm-memspeed: official download site www.kreuzholzen.de is gone, request for ptx mirror
Package: arm-memspeed The arm-memspeed rule refers to download URL http://www.kreuzholzen.de/src/arm-memspeed/arm-memspeed-1.0.tar.bz2 which fails, as kreuzholzen.de is gone. According to DENIC, the domain is free. Package is also not mirrored by PTX, therefore download fails. I found a copy of the source at https://download.phytec.de/Software/Linux/Yocto/SourceMirror/arm-memspeed-1.0.tar.bz2 with matching MD5. Might I ask Pengutronix to add this package to their mirror? Respectively host it? After a quick search, I did not find any other source, let alone some official place. Thanks in advance, Andreas target: arm-memspeed-1.0.tar.bz2 --2023-04-17 21:18:19-- http://www.kreuzholzen.de/src/arm-memspeed/arm-memspeed-1.0.tar.bz2 Resolving www.kreuzholzen.de (www.kreuzholzen.de)... failed: Name or service not known. wget: unable to resolve host address 'www.kreuzholzen.de' --2023-04-17 21:18:19-- https://www.pengutronix.de/software/ptxdist/temporary-src/arm-memspeed-1.0.tar.bz2 Resolving www.pengutronix.de (www.pengutronix.de)... 2a01:4f9:2a:2c17:5054:ff:fe65:8c93, 95.216.103.100 Connecting to www.pengutronix.de (www.pengutronix.de)|2a01:4f9:2a:2c17:5054:ff:fe65:8c93|:443... connected. HTTP request sent, awaiting response... 307 Temporary Redirect Location: https://public.pengutronix.de/mirror/software/ptxdist/temporary-src/arm-memspeed-1.0.tar.bz2 [following] --2023-04-17 21:18:19-- https://public.pengutronix.de/mirror/software/ptxdist/temporary-src/arm-memspeed-1.0.tar.bz2 Resolving public.pengutronix.de (public.pengutronix.de)... 2a01:4f9:2a:2c17:5054:ff:fe65:8c93, 95.216.103.100 Connecting to public.pengutronix.de (public.pengutronix.de)|2a01:4f9:2a:2c17:5054:ff:fe65:8c93|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2023-04-17 21:18:19 ERROR 404: Not Found. Could not download package URL: http://www.kreuzholzen.de/src/arm-memspeed/arm-memspeed-1.0.tar.bz2 -- carpe noctem engineering Ingenieurbuero fuer Hard- & Software-Entwicklung Andreas Pretzsch Dipl.-Ing. (FH) Andreas PretzschTel. +49-(0)711-3908735-7 Tuebinger Strasse 63Fax: +49-(0)711-3908735-9 70178 Stuttgart, Germanyemail: a...@cn-eng.de
Re: [ptxdist] [PATCH] at91bootstrap2: make targetinstall v4.x compatible
On 17.04.23 13:51, Ahmad Fatoum wrote: > The binaries directory, where artifacts were previously written to is > now beneath build/ by default[1]: > > BUILDDIR ?= ./build > BINDIR:=$(BUILDDIR)/binaries > > Supply BUILDDIR=. after the make command to return to the old directory > scheme. This should have no effect on AT91Bootstrap v3.x and older > as BUILDDIR was first added in v4.0.0[1]. [1]: https://github.com/linux4sam/at91bootstrap/commit/814f3bdab515287fbb0d972d89d228748613ae91 is what I meant to reference. Please let me know if I should resend. Thanks, Ahmad > > Signed-off-by: Ahmad Fatoum > --- > rules/at91bootstrap2.make | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/rules/at91bootstrap2.make b/rules/at91bootstrap2.make > index dcb1157b17f1..c36e30305a92 100644 > --- a/rules/at91bootstrap2.make > +++ b/rules/at91bootstrap2.make > @@ -35,7 +35,7 @@ AT91BOOTSTRAP2_WRAPPER_BLACKLIST := \ > AT91BOOTSTRAP2_MAKE_ENV := \ > CROSS_COMPILE=$(BOOTLOADER_CROSS_COMPILE) \ > HOSTCC=$(HOSTCC) > -AT91BOOTSTRAP2_MAKE_OPT := V=$(PTXDIST_VERBOSE) > +AT91BOOTSTRAP2_MAKE_OPT := V=$(PTXDIST_VERBOSE) BUILDDIR=. > > ifdef PTXCONF_AT91BOOTSTRAP2 > $(AT91BOOTSTRAP2_CONFIG): -- 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- |
[ptxdist] [PATCH] at91bootstrap2: make targetinstall v4.x compatible
The binaries directory, where artifacts were previously written to is now beneath build/ by default[1]: BUILDDIR ?= ./build BINDIR:=$(BUILDDIR)/binaries Supply BUILDDIR=. after the make command to return to the old directory scheme. This should have no effect on AT91Bootstrap v3.x and older as BUILDDIR was first added in v4.0.0[1]. Signed-off-by: Ahmad Fatoum --- rules/at91bootstrap2.make | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules/at91bootstrap2.make b/rules/at91bootstrap2.make index dcb1157b17f1..c36e30305a92 100644 --- a/rules/at91bootstrap2.make +++ b/rules/at91bootstrap2.make @@ -35,7 +35,7 @@ AT91BOOTSTRAP2_WRAPPER_BLACKLIST := \ AT91BOOTSTRAP2_MAKE_ENV := \ CROSS_COMPILE=$(BOOTLOADER_CROSS_COMPILE) \ HOSTCC=$(HOSTCC) -AT91BOOTSTRAP2_MAKE_OPT := V=$(PTXDIST_VERBOSE) +AT91BOOTSTRAP2_MAKE_OPT := V=$(PTXDIST_VERBOSE) BUILDDIR=. ifdef PTXCONF_AT91BOOTSTRAP2 $(AT91BOOTSTRAP2_CONFIG): -- 2.39.2
[ptxdist] [PATCH] mesalib: intel and amd vulkan drivers require host-glslang
Add a host-glslang dependency to make glslangValidator available to the AMD and Intel Vulkan driver builds. Signed-off-by: Philipp Zabel --- rules/mesalib.in | 2 ++ 1 file changed, 2 insertions(+) diff --git a/rules/mesalib.in b/rules/mesalib.in index 7372c2fa0c05..cf9619c85241 100644 --- a/rules/mesalib.in +++ b/rules/mesalib.in @@ -8,6 +8,8 @@ menuconfig MESALIB select HOST_MAKEDEPEND select HOST_SYSTEM_PYTHON3 select HOST_SYSTEM_PYTHON3_MAKO + select HOST_GLSLANG if MESALIB_VULKAN_AMD + select HOST_GLSLANG if MESALIB_VULKAN_INTEL select HOST_GLSLANG if MESALIB_VULKAN_OVERLAY select GCCLIBS select GCCLIBS_CXX -- 2.39.2
[ptxdist] [PATCH] configure_helper: ignore new Meson 1.1.0 builtin options
Ignore new Meson builtin options "licensedir" (since 1.1.0) and "vsenv" (since 1.1.0). Signed-off-by: Philipp Zabel --- scripts/configure_helper.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/scripts/configure_helper.py b/scripts/configure_helper.py index e6907cd4eb21..d5abc5a02c1a 100755 --- a/scripts/configure_helper.py +++ b/scripts/configure_helper.py @@ -144,6 +144,7 @@ meson_blacklist = [ "install_umask", "layout", "libexecdir", + "licensedir", "localedir", "localstatedir", "mandir", @@ -160,6 +161,7 @@ meson_blacklist = [ "sysconfdir", "unity", "unity_size", + "vsenv", "warning_level", "werror", "wrap_mode", -- 2.39.2
Re: [ptxdist] [PATCH 1/3] rules: opensc: Version bumb to 0.23.0
On 13-04-2023 15:57, Michael Olbrich wrote:
On Thu, Apr 13, 2023 at 09:25:54AM +0200, Robin van der Gracht wrote:
...
+From 9294183e07ff4944e3f5e590f343f5727636767e Mon Sep 17 00:00:00 2001
+From: Jakub Jelen
+Date: Thu, 1 Dec 2022 20:08:53 +0100
+Subject: [PATCH] pkcs11-tool: Fix private key import
+
+---
+ src/tools/pkcs11-tool.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/tools/pkcs11-tool.c b/src/tools/pkcs11-tool.c
+index aae205fe..cfee8526 100644
+--- a/src/tools/pkcs11-tool.c
b/src/tools/pkcs11-tool.c
+@@ -3669,13 +3669,13 @@ parse_rsa_pkey(EVP_PKEY *pkey, int private, struct
rsakey_info *rsa)
+ RSA_get0_factors(r, _p, _q);
+ RSA_get0_crt_params(r, _dmp1, _dmq1, _iqmp);
+ #else
+- if (EVP_PKEY_get_bn_param(pkey, OSSL_PKEY_PARAM_RSA_FACTOR1,
_d) != 1 ||
++ if (EVP_PKEY_get_bn_param(pkey, OSSL_PKEY_PARAM_RSA_D, _d) !=
1 ||
+ EVP_PKEY_get_bn_param(pkey, OSSL_PKEY_PARAM_RSA_FACTOR1,
_p) != 1 ||
+ EVP_PKEY_get_bn_param(pkey, OSSL_PKEY_PARAM_RSA_FACTOR2,
_q) != 1 ||
+ EVP_PKEY_get_bn_param(pkey, OSSL_PKEY_PARAM_RSA_EXPONENT1,
_dmp1) != 1 ||
+ EVP_PKEY_get_bn_param(pkey, OSSL_PKEY_PARAM_RSA_EXPONENT2,
_dmq1) != 1 ||
+- EVP_PKEY_get_bn_param(pkey, OSSL_PKEY_PARAM_RSA_EXPONENT3,
_iqmp) != 1) {
+ util_fatal("OpenSSL error during RSA private key
parsing");
++ EVP_PKEY_get_bn_param(pkey,
OSSL_PKEY_PARAM_RSA_COEFFICIENT1, _iqmp) != 1) {
This is broken. Probably a bad conflict resolution. The next upstream
commit fixes this. So far it looks promising. I'll do some more testing and
clean it up.
I only compile tested the patch.
Ok, thanks!
Kind regards,
Robin
