Re: [ptxdist] rootfs: package
On Mon, Dec 03, 2018 at 11:38:46PM +0100, Andreas Friesen wrote: > Hello everyone, > > it's work now. Here is a little patch. > > > --- /usr/local/lib/ptxdist-2018.11.0/rules/host-opkg.make 2018-11-22 > 20:12:56.0 +0100 > > +++ rules/host-opkg.make2018-12-03 23:36:48.214811901 +0100 > @@ -31,7 +31,6 @@ > # > HOST_OPKG_CONF_TOOL:= autoconf > HOST_OPKG_CONF_OPT := \ > - $(HOST_AUTOCONF) \ > --disable-libopkg-api \ > --disable-static \ > --disable-pathfinder \ > @@ -45,4 +44,6 @@ > --without-libsolv \ > --without-static-libopkg > > +# $(HOST_AUTOCONF) \ > + > # vim: syntax=make This just removes opkg from your PATH. Did you rebuild the BSP afterwards? Maybe you have opkg somewhere else in PATH. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] rootfs: package
On Thu, Nov 29, 2018 at 08:35:09AM +0100, Andreas Friesen wrote: > ... > Hello everyone, > > I migrated my project from 2017.05.0 to 2018.11.0 without any troubles, but > "ptxdist images" has a problem with rootfs package. Options > PTXCONF_ROOTFS_RUN=y > PTXCONF_ROOTFS_VAR_RUN=y are active and I don't have any packages, which > install /run or /var/run as a directory. I checked all packages with > manually extract with : > ar x $package ; tar -xf ./data.tar.gz ; > > rootfs_1.0.0_armhf.ipk > ... > drwx-- 240 Nov 1 01:00 root > drwxr-xr-x 240 Nov 1 01:00 run > drwxr-xr-x 240 Nov 1 01:00 sys > ... > drwxr-xr-x 2 40 Nov 1 01:00 var/log > lrwxrwxrwx 1 6 Nov 1 01:00 var/run -> ../run > drwxr-xr-x 2 40 Nov 1 01:00 var/tmp > > also, rootfs package looks great for me, but what is wrong with "ptxdist > images" > ... > Installing usr-rootfs (1.0) on root. > InstallinCollected errors: > * check_data_file_clashes: Package rootfs wants to install file > /home/faix/ptx-multi/platform-soc/build-target/image-nor-mxfs4/var/run > But that path is currently a directory > * opkg_solver_install: Cannot install package rootfs. > g luacjson (1.0.0) on root. > > Installing rootfs (1.0.0) on root. > To remove package debris, try `opkg remove rootfs`. > To re-attempt the install, try `opkg install rootfs`. > ... > Configuring libndp. > make: *** [/home/faix/ptx-multi/rules/image-ubifs-mxfs4.make:12: > /home/ffaix/ptx-multi/platform-soc/images/root-mxfs4.ubifs] Error 255 I think build-target/image-nor-mxfs4/ should still contain the image content if image creation fails. Is /var/run empty there? Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] package: What is wrong with host-unfs3
On Tue, Dec 04, 2018 at 12:38:00AM +0100, Andreas Friesen wrote: > After BSP upgrade to 2018.11.0 I've got this error: > > --- > target: host-unfs3.install.post > --- > > finished target host-unfs3.install.post > > ptxdist: error: ethtool is not a package or not selected > > /usr/local/lib/ptxdist-2018.11.0/rules/post/ptxd_make_nfsd.make:12: recipe > for target 'ptxd_make_nfsd' failed > make: *** [ptxd_make_nfsd] Error 1 This is now fixed in master. For a workaround for the latest release see my comment in the thread 'ptxdist upgrade from v2014.12.0 to latest -> error'. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] package: What is wrong with host-unfs3
Hi, After BSP upgrade to 2018.11.0 I've got this error: --- target: host-unfs3.install.post --- finished target host-unfs3.install.post ptxdist: error: ethtool is not a package or not selected /usr/local/lib/ptxdist-2018.11.0/rules/post/ptxd_make_nfsd.make:12: recipe for target 'ptxd_make_nfsd' failed make: *** [ptxd_make_nfsd] Error 1 ___ ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] rootfs: package
Hello everyone, it's work now. Here is a little patch. --- /usr/local/lib/ptxdist-2018.11.0/rules/host-opkg.make 2018-11-22 20:12:56.0 +0100 +++ rules/host-opkg.make2018-12-03 23:36:48.214811901 +0100 @@ -31,7 +31,6 @@ # HOST_OPKG_CONF_TOOL:= autoconf HOST_OPKG_CONF_OPT := \ - $(HOST_AUTOCONF) \ --disable-libopkg-api \ --disable-static \ --disable-pathfinder \ @@ -45,4 +44,6 @@ --without-libsolv \ --without-static-libopkg +# $(HOST_AUTOCONF) \ + # vim: syntax=make Am Do., 29. Nov. 2018 um 08:35 Uhr schrieb Andreas Friesen < ms.f...@gmail.com>: > ... > Hello everyone, > > I migrated my project from 2017.05.0 to 2018.11.0 without any troubles, > but > "ptxdist images" has a problem with rootfs package. Options > PTXCONF_ROOTFS_RUN=y > PTXCONF_ROOTFS_VAR_RUN=y are active and I don't have any packages, which > install /run or /var/run as a directory. I checked all packages with > manually extract with : > ar x $package ; tar -xf ./data.tar.gz ; > > rootfs_1.0.0_armhf.ipk > ... > drwx-- 240 Nov 1 01:00 root > drwxr-xr-x 240 Nov 1 01:00 run > drwxr-xr-x 240 Nov 1 01:00 sys > ... > drwxr-xr-x 2 40 Nov 1 01:00 var/log > lrwxrwxrwx 1 6 Nov 1 01:00 var/run -> ../run > drwxr-xr-x 2 40 Nov 1 01:00 var/tmp > > also, rootfs package looks great for me, but what is wrong with "ptxdist > images" > ... > Installing usr-rootfs (1.0) on root. > InstallinCollected errors: > * check_data_file_clashes: Package rootfs wants to install file > /home/faix/ptx-multi/platform-soc/build-target/image-nor-mxfs4/var/run > But that path is currently a directory > * opkg_solver_install: Cannot install package rootfs. > g luacjson (1.0.0) on root. > > Installing rootfs (1.0.0) on root. > To remove package debris, try `opkg remove rootfs`. > To re-attempt the install, try `opkg install rootfs`. > ... > Configuring libndp. > make: *** [/home/faix/ptx-multi/rules/image-ubifs-mxfs4.make:12: > /home/ffaix/ptx-multi/platform-soc/images/root-mxfs4.ubifs] Error 255 > > - Andreas > ___ ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] ptxdist upgrade from v2014.12.0 to latest -> error
Hello, thank you for your quick response. That fixed the problem. regards Hubert Am Mo., 3. Dez. 2018 um 17:55 Uhr schrieb Michael Olbrich < m.olbr...@pengutronix.de>: > Hello, > > On Mon, Dec 03, 2018 at 05:23:17PM +0100, Hubert Feurstein wrote: > > I've upgraded my BSP from PTXdist v2014.12.2 to the latest master > version. > > Building the BSP produces now the following error at the very end: > > > > [...] > > --- > > target: host-genext2fs.install.post > > --- > > > > finished target host-genext2fs.install.post > > finished target world.targetinstall > > > > ptxdist: error: sysupdate is not a package or not selected > > > > > .../build-tools/ptxdist/rules/post/ptxd_make_image_fix_permissions.make:21: > > recipe for target '...bsp/platform-mx6/state/ptx_image_fix_permissions' > > failed > > make: *** [...bsp/platform-mx6/state/ptx_image_fix_permissions] Error 1 > > -- > > > > The package 'sysupdate' is a package and it is selected. If I deselect > this > > package and run 'ptxdist go' again, then I get the same error with an > other > > package reported. Running 'ptxdist images' afterwards still works as > > expected. Any help is very appreciated. > > Do you need initial device nodes in the nfsroot? This is usually not needed > any more. If not, just disable PTXCONF_FIX_PERMISSIONS. There is a bug here > that breaks the sanity check that produces the error message you get. > > Michael > > -- > Pengutronix e.K. | | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | > > ___ > ptxdist mailing list > ptxdist@pengutronix.de ___ ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] ptxdist upgrade from v2014.12.0 to latest -> error
Hello, On Mon, Dec 03, 2018 at 05:23:17PM +0100, Hubert Feurstein wrote: > I've upgraded my BSP from PTXdist v2014.12.2 to the latest master version. > Building the BSP produces now the following error at the very end: > > [...] > --- > target: host-genext2fs.install.post > --- > > finished target host-genext2fs.install.post > finished target world.targetinstall > > ptxdist: error: sysupdate is not a package or not selected > > .../build-tools/ptxdist/rules/post/ptxd_make_image_fix_permissions.make:21: > recipe for target '...bsp/platform-mx6/state/ptx_image_fix_permissions' > failed > make: *** [...bsp/platform-mx6/state/ptx_image_fix_permissions] Error 1 > -- > > The package 'sysupdate' is a package and it is selected. If I deselect this > package and run 'ptxdist go' again, then I get the same error with an other > package reported. Running 'ptxdist images' afterwards still works as > expected. Any help is very appreciated. Do you need initial device nodes in the nfsroot? This is usually not needed any more. If not, just disable PTXCONF_FIX_PERMISSIONS. There is a bug here that breaks the sanity check that produces the error message you get. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] ptxdist upgrade from v2014.12.0 to latest -> error
Hi, I've upgraded my BSP from PTXdist v2014.12.2 to the latest master version. Building the BSP produces now the following error at the very end: [...] --- target: host-genext2fs.install.post --- finished target host-genext2fs.install.post finished target world.targetinstall ptxdist: error: sysupdate is not a package or not selected .../build-tools/ptxdist/rules/post/ptxd_make_image_fix_permissions.make:21: recipe for target '...bsp/platform-mx6/state/ptx_image_fix_permissions' failed make: *** [...bsp/platform-mx6/state/ptx_image_fix_permissions] Error 1 -- The package 'sysupdate' is a package and it is selected. If I deselect this package and run 'ptxdist go' again, then I get the same error with an other package reported. Running 'ptxdist images' afterwards still works as expected. Any help is very appreciated. regards, Hubert ___ ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] [PATCH] lm-sensors: version bump 3.4.0 -> 3.5.0
Hei hei, Am Montag, 3. Dezember 2018, 12:58:11 CET schrieb Lucas Stach: > - version bump > - switch to project github repo > > Signed-off-by: Lucas Stach Acked-by: Alexander Dahl Greets Alex ___ ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] [PATCH] lm-sensors: version bump 3.4.0 -> 3.5.0
- version bump - switch to project github repo Signed-off-by: Lucas Stach --- rules/lm_sensors.make | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/rules/lm_sensors.make b/rules/lm_sensors.make index 5bede75dad08..a80ffdc13807 100644 --- a/rules/lm_sensors.make +++ b/rules/lm_sensors.make @@ -17,13 +17,13 @@ PACKAGES-$(PTXCONF_LM_SENSORS) += lm_sensors # # Paths and names # -LM_SENSORS_VERSION := 3.4.0 -LM_SENSORS_TAG := V3-4-0 -LM_SENSORS_MD5 := 1e9f117cbfa11be1955adc96df71eadb +LM_SENSORS_VERSION := 3.5.0 +LM_SENSORS_TAG := V3-5-0 +LM_SENSORS_MD5 := 37981f5d3a0f649381529cb41c0f1ff3 LM_SENSORS := lm_sensors-$(LM_SENSORS_VERSION) LM_SENSORS_SUFFIX := tar.gz LM_SENSORS_URL := \ - https://github.com/groeck/lm-sensors/archive/$(LM_SENSORS_TAG).$(LM_SENSORS_SUFFIX) + https://github.com/lm-sensors/lm-sensors/archive/$(LM_SENSORS_TAG).$(LM_SENSORS_SUFFIX) LM_SENSORS_SOURCE := $(SRCDIR)/$(LM_SENSORS).$(LM_SENSORS_SUFFIX) LM_SENSORS_DIR := $(BUILDDIR)/$(LM_SENSORS) LM_SENSORS_LICENSE := GPL-2.0-or-later AND LGPL-2.1-or-later -- 2.19.1 ___ ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] [PATCH 2/5] ptxdist: add tpm2-tss version 2.1.0
Hello Marc, On Wed, Nov 28, 2018 at 09:02:10AM +0100, Marc Kleine-Budde wrote: > On 11/26/18 11:23 AM, Thorsten K. Scherer wrote: > > Signed-off-by: Thorsten K. Scherer > > --- > > ...rom-the-list-of-libs-to-link-against.patch | 21 ++ > > patches/tpm2-tss-2.1.0/series | 4 ++ > > rules/tpm.in | 5 ++ > > rules/tpm2-tss.in | 22 +++ > > rules/tpm2-tss.make | 66 +++ > > 5 files changed, 118 insertions(+) > > create mode 100644 > > patches/tpm2-tss-2.1.0/0001-drop-lgcrypt-from-the-list-of-libs-to-link-against.patch > > create mode 100644 patches/tpm2-tss-2.1.0/series > > create mode 100644 rules/tpm.in > > create mode 100644 rules/tpm2-tss.in > > create mode 100644 rules/tpm2-tss.make > > > > diff --git > > a/patches/tpm2-tss-2.1.0/0001-drop-lgcrypt-from-the-list-of-libs-to-link-against.patch > > > > b/patches/tpm2-tss-2.1.0/0001-drop-lgcrypt-from-the-list-of-libs-to-link-against.patch > > new file mode 100644 > > index 000..0230570 > > --- /dev/null > > +++ > > b/patches/tpm2-tss-2.1.0/0001-drop-lgcrypt-from-the-list-of-libs-to-link-against.patch > > @@ -0,0 +1,21 @@ > > +From: =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?= > > +Date: Fri, 12 Oct 2018 11:13:42 +0200 > > +Subject: [PATCH] drop -lgcrypt from the list of libs to link against > > + > > +If --with-crypto=ossl is used -lgcrypt is wrong. There shouldn't be any > > need > > +to explicitly tell the linker because the library already depends the > > chosen > > +crypto lib > > S-o-b missing I'm unsure why you think a S-o-b is necessary here. The upstream project requires a S-o-b by the submitter (who is not necessarily the patch author) only when the patch is sent to them for application. And in my eyes the S-o-b on the ptxdist-patch already covers that the whole content (so including the added patch file) is compatible with ptxdist's license. Can you clearify? Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ | ___ ptxdist mailing list ptxdist@pengutronix.de
