[ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2022.10.2 and 2023.07.1 released
Hi, I'm happy to announce that I've just released OSELAS.Toolchain-2022.10.2 and 2023.07.1. This is a bugfix only release. There are no major update. The relevant changes are: - gcc was updated to the 12-20231117 and 13-20231118 snapshot releases. Note, that for the 2023.07.1 toolchain the reported version is now 13.2.1 so the platformconfig in PTXdist BSPs must be updated accordingly. - glibc was updated to 2.36-121-g88d5d70b1e89 and 2.37-48-g8e20aedfd7fc in the respective stable branch. - All patches from the binutils stable branches that seemed relevant have been cherry-picked. - The gcc fortran compiler is now enabled in all Linux toolchains Download the release here: https://public.pengutronix.de/oselas/toolchain/ Debian / Ubuntu Packages will be available at http://debian.pengutronix.de/ For the binary packages, the plan is the same as for the corresponding major release. With two toolchain releases there is more to build so it will take a bit longer until all packages are done. Enjoy, Michael Olbrich -- 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- | signature.asc Description: PGP signature
[ptxdist] [PATCH] networkmanager: Version bump 1.30.4 to 1.44.2
dnssec_trigger and iptables configure options has been removed select PPP_MS_CHAP if NETWORKMANAGER_PPP is enabled to fix compile error: ../NetworkManager-1.44.2/src/core/ppp/nm-pppd-compat.c:50:10: fatal error: pppd/chap_ms.h: No such file or directory 50 | #include Signed-off-by: Lars Pedersen --- Version 1.30.4 was getting pretty old and with this patch it will match the one in Fedora 39. Surprisingly no major changes in configure options. Note: Updating ppp to version 2.5.0 seemed pretty straight forward, but I ran into issue https://github.com/ppp-project/ppp/issues/419. I'll try to send a ppp patch when 2.5.1 is released. rules/networkmanager.in | 1 + rules/networkmanager.make | 6 ++ 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/rules/networkmanager.in b/rules/networkmanager.in index e9af26729..8c5e8ad2e 100644 --- a/rules/networkmanager.in +++ b/rules/networkmanager.in @@ -24,6 +24,7 @@ menuconfig NETWORKMANAGER select POLKIT if NETWORKMANAGER_POLKIT select PPP if NETWORKMANAGER_PPP select PPP_PLUGINS if NETWORKMANAGER_PPP + select PPP_MS_CHAP if NETWORKMANAGER_PPP select READLINE if NETWORKMANAGER_NMCLI select SYSTEMD if NETWORKMANAGER_SYSTEMD_UNIT select UDEV diff --git a/rules/networkmanager.make b/rules/networkmanager.make index 9b47fadad..af310bd13 100644 --- a/rules/networkmanager.make +++ b/rules/networkmanager.make @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_NETWORKMANAGER) += networkmanager # # Paths and names # -NETWORKMANAGER_VERSION := 1.30.4 -NETWORKMANAGER_MD5 := 8ce53a38356864832f7f10ad46fcde27 +NETWORKMANAGER_VERSION := 1.44.2 +NETWORKMANAGER_MD5 := bd6c9cb0ecd0fb7f516cde7bf4dee3fb NETWORKMANAGER := NetworkManager-$(NETWORKMANAGER_VERSION) NETWORKMANAGER_SUFFIX := tar.xz NETWORKMANAGER_URL := $(call ptx/mirror, GNOME, NetworkManager/$(basename $(NETWORKMANAGER_VERSION))/$(NETWORKMANAGER).$(NETWORKMANAGER_SUFFIX)) @@ -47,7 +47,6 @@ NETWORKMANAGER_CONF_OPT = \ -Ddhcpcanon=false \ -Ddhcpcd=false \ -Ddnsmasq=/usr/sbin/dnsmasq \ - -Ddnssec_trigger=/bin/true \ -Ddocs=false \ -Debpf=false \ -Dfirewalld_zone=false \ @@ -55,7 +54,6 @@ NETWORKMANAGER_CONF_OPT = \ -Difcfg_rh=false \ -Difupdown=true \ -Dintrospection=$(call ptx/truefalse,PTXCONF_NETWORKMANAGER_INTROSPECTION) \ - -Diptables=/usr/sbin/iptables \ -Diwd=false \ -Dkernel_firmware_dir=/lib/firmware \ -Dld_gc=true \ -- 2.41.0
[ptxdist] [PATCH] rules: template-src-make-prog-make: make use of the 'execute' macro
It does everything that is written out explicitely here; additionally it will also respect @PACKAGE@_SUBDIR if it should be set. Signed-off-by: Roland Hieber --- rules/templates/template-src-make-prog-make | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/rules/templates/template-src-make-prog-make b/rules/templates/template-src-make-prog-make index 50957c0f83ee..7227916e234f 100644 --- a/rules/templates/template-src-make-prog-make +++ b/rules/templates/template-src-make-prog-make @@ -92,8 +92,7 @@ $(STATEDIR)/@package@.targetinstall: $(STATEDIR)/@package@.clean: @$(call targetinfo) - @-cd $(@PACKAGE@_DIR) && \ - $(@PACKAGE@_ENV) $(@PACKAGE@_PATH) $(MAKE) clean + @-$(call execute, @PACKAGE@, $(MAKE) clean) @$(call clean_pkg, @PACKAGE@) # vim: syntax=make -- 2.39.2
[ptxdist] [PATCH] nbd: version bump 3.21 -> 3.25
Since release 3.25, the official releases of nbd are on GitHub and no longer uploaded to sourceforge. Support for the Sockets Direct Protocol (SDP) has been dropped from upstream since the protocol is deprecated. Signed-off-by: Michael Tretter --- rules/nbd.make | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/rules/nbd.make b/rules/nbd.make index 4d604d0fa5c7..ab5f2b7e93da 100644 --- a/rules/nbd.make +++ b/rules/nbd.make @@ -14,11 +14,11 @@ PACKAGES-$(PTXCONF_NBD) += nbd # # Paths and names # -NBD_VERSION:= 3.21 -NBD_MD5:= c51c4c500fe1ed84c3d5d5dd2ca71d23 +NBD_VERSION:= 3.25 +NBD_MD5:= fc885361c00ac4de2c45d651c48bd937 NBD:= nbd-$(NBD_VERSION) NBD_SUFFIX := tar.xz -NBD_URL:= $(call ptx/mirror, SF, nbd/$(NBD).$(NBD_SUFFIX)) +NBD_URL:= https://github.com/NetworkBlockDevice/nbd/releases/download/$(NBD)/$(NBD).$(NBD_SUFFIX) NBD_SOURCE := $(SRCDIR)/$(NBD).$(NBD_SUFFIX) NBD_DIR:= $(BUILDDIR)/$(NBD) NBD_LICENSE:= GPL-2.0-only @@ -34,7 +34,6 @@ NBD_CONF_OPT := \ --$(call ptx/endis, PTXCONF_GLOBAL_LARGE_FILE)-lfs \ --disable-syslog \ --disable-debug \ - --disable-sdp \ --disable-gznbd \ --disable-manpages \ --without-gnutls \ -- 2.39.2
Re: [ptxdist] [RFC PATCH 0/1] building qmake based target packages
Hello Michael, Am Fri, Nov 10, 2023 at 08:51:01AM +0100 schrieb Michael Olbrich: > On Tue, Oct 17, 2023 at 01:35:14PM +0200, Alexander Dahl wrote: > > Hello everyone, > > > > I currently have some kind of weird requirement: building a target > > package with qmake, but not linking against Qt. It's a fork of RTKlib > > which is itself a university project (with hand written makefiles, but > > not for the part I'm interested in): > > > > https://github.com/rtklibexplorer/RTKLIB/releases/tag/b34h > > > > I actually achieved building it with the attached make rule. Note it > > has a dependency to QT5, but I had to manually add the Qt mkspec file > > ptxdist creates as an option to the _CONF_OPT variable. > > > > Two things are bad about this: > > > > 1.) I don't think it should be necessary to let the make rule set the > > correct mkspec file. There is only one and IMHO ptxdist should handle > > this internally if CONF_TOOL is qmake? > > I'm pretty sure you're calling the wrong qmake here. You need to modify > PATH the same way e.g. rules/qwt5.make does. This works, thanks. (If not setting that, the qmake of my host system was taken. Double checked that by removing that qmake for now.) > > 2.) rather large Qt libraries are installed to the target now. I guess > > I might be able to avoid this by setting 'select QT5 if BUILDTIME' in > > the in rule, but I would have expected HOST_QT5 to be sufficient. This > > does not work however for two reasons: a) ptxdist complains it needs QT5 > > if CONF_TOOL is qmake and b) if I only select HOST_QT5 that mkspec is > > not generated. > > Do you need qmake from qt5 or would qt6 work as well? We already have a > host-qt6 package and if we build the binary there and split out the qmake > config stuff from qt6 into a new cross-qmake package. Tested with 'select QT5' and 'select QT6' now and both work. Only doing 'select HOST_QT5' or 'HOST_QT6' yields this: [ 35/171] started : rtklib-demo5.prepare ptxdist: error: 'rtklib-demo5' uses 'qmake' but does not select 'qt5' or 'qt6' (With ptxdist-2023.03.0 at least.) > It would need to copy the mkspecs from the host package I think before > adding the custom mkspecs stuff. This is not yet in place, right? At least I could not see any related changes between ptxdist-2023.05.0 and master. Greets Alex > > Michael > > > I saw ptxdist having nearly zero packages selecting QT5, and none > > requiring HOST_QT5 (?) so it's difficult to learn from examples here. > > Maybe this usecase is quite esoteric? Don't know. > > > > In the end I would only need qmake, nothing more. That one generates a > > Makefile which is then used to compile the package. > > > > Would take directions to improve ptxdist for qmake based packages. > > > > Greets > > Alex > > > > Alexander Dahl (1): > > WIP: rtklib-demo5: Add new package > > > > rules/rtklib-demo5.in | 23 > > rules/rtklib-demo5.make | 58 + > > 2 files changed, 81 insertions(+) > > create mode 100644 rules/rtklib-demo5.in > > create mode 100644 rules/rtklib-demo5.make > > > > > > base-commit: 90875f8af4f6f1dd9f8eda71df8e8a90866f9839 > > -- > > 2.30.2 > > > > > > > > -- > 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- |
