Re: [ptxdist] websocat rust package

On Fri, Aug 4, 2023 at 3:01 PM Ladislav Michl wrote: > > Hi, > > On Fri, Aug 04, 2023 at 10:54:59AM -0400, Jon Ringle wrote: > > I'm trying to create a new package to build websocat ( > > https://github.com/vi/websocat). > > Here is the websocat.make file I have n

[ptxdist] websocat rust package

I'm trying to create a new package to build websocat ( https://github.com/vi/websocat). Here is the websocat.make file I have now: # # We provide this package # PACKAGES-$(PTXCONF_WEBSOCAT) += websocat # # Paths and names # WEBSOCAT_VERSION := 1.11.0 WEBSOCAT_MD5 :=

Re: [ptxdist] ipk with a postinst are not bitwise idempotent

py of scripts/lib/ptxd_make_world_common.sh with the setting of SOURCE_DATE_EPOCH removed. That fixed the issue for me. -Jon On Fri, Sep 9, 2022 at 2:50 PM Jon Ringle wrote: > I added `set -x` for debugging to ptxd_make_reproducible() where > SOURCE_DATE_EPOCH is exported: > >

Re: [ptxdist] ipk with a postinst are not bitwise idempotent

s, libtirpc, protobuf, pugixml, qt4, sdbus-cpp, sqlite, systemd, util-linux-ng, zlib install_init: preinst not available install_init: postinst not available install_init: prerm not available install_init: postrm not available install_fixup: @PRIORITY@ -> optional ... done. install_fix

Re: [ptxdist] ipk with a postinst are not bitwise idempotent

AM Jon Ringle wrote: > > > On Fri, Sep 9, 2022 at 11:20 AM Jon Ringle wrote: > >> I've discovered that if you have a package that includes a postinst >> script, the resulting ipk file will no longer be bitwise idempotent because >> the timestamps in the

Re: [ptxdist] ipk with a postinst are not bitwise idempotent

On Fri, Sep 9, 2022 at 11:20 AM Jon Ringle wrote: > I've discovered that if you have a package that includes a postinst > script, the resulting ipk file will no longer be bitwise idempotent because > the timestamps in the files inside of control.tar.gz and data.tar.gz will &

[ptxdist] ipk with a postinst are not bitwise idempotent

I've discovered that if you have a package that includes a postinst script, the resulting ipk file will no longer be bitwise idempotent because the timestamps in the files inside of control.tar.gz and data.tar.gz will now have the the timestamps at build time rather than from SOURCE_DATE_EPOCH.

Re: [ptxdist] ptxdist make license-report failing

On Wed, Dec 8, 2021 at 8:11 PM Michael Olbrich wrote: > Hi, > > On Tue, Nov 30, 2021 at 09:18:25AM +0100, Nicholai Juul Hansen wrote: > > The license report scripts are not able to handle packages with #md5= in > > the URL, which is not uncommon in the python packages. > > As far as I can tell,

[ptxdist] ptxdist make license-report failing

Hello. I'm trying to build the license-report and it is failing. I'm not sure how to proceed with troubleshooting this issue. Thanks, -Jon jring-t580-gns3 ~/git/rootfs$ ptxdist make license-report -- target: license-report.pdf -- Extracting

Re: [ptxdist] [PATCH] host-systemd: Add option to install dev files

On Thu, Jul 8, 2021 at 12:59 AM Michael Olbrich wrote: > On Wed, Jul 07, 2021 at 05:06:56PM -0400, Jon Ringle wrote: > > On Fri, Jun 25, 2021 at 5:41 AM Michael Olbrich < > m.olbr...@pengutronix.de> > > wrote: > > > > > On Tue, Jun 22, 2021 at

Re: [ptxdist] [PATCH] host-systemd: Add option to install dev files

Hi Michael On Fri, Jun 25, 2021 at 5:41 AM Michael Olbrich wrote: > On Tue, Jun 22, 2021 at 04:35:04PM +, j...@ringle.org wrote: > > From: Jon Ringle > > > > Doing a full install that include dev files is > > helpful if a project needs this support. > &g

Re: [ptxdist] problem configuring python3

On Wed, Jun 16, 2021 at 9:02 AM Michael Olbrich wrote: > > Did you build host-python3 in this container? > > $ grep host-python3\\. platform-ec1k/logfile target: host-python3.6bcbacf952d0391d7b67701a157ca622.srchash finished target host-python3.6bcbacf952d0391d7b67701a157ca622.srchash target:

Re: [ptxdist] problem configuring python3

On Wed, Jun 16, 2021 at 8:30 AM Juergen Borleis wrote: > Hi Jon, > > Am Mittwoch, den 16.06.2021, 08:05 -0400 schrieb Jon Ringle: > > Am Dienstag, den 15.06.2021, 16:18 +0200 schrieb Michael Olbrich: > > > > […] > > > > I'm not sure why it would be look

Re: [ptxdist] problem configuring python3

On Tue, Jun 15, 2021 at 9:54 AM Michael Olbrich wrote: > On Tue, Jun 15, 2021 at 08:17:36AM -0400, Jon Ringle wrote: > > On Tue, Jun 15, 2021 at 8:08 AM Michael Olbrich < > m.olbr...@pengutronix.de> > > wrote: > > > On Tue, Jun 15, 2021 at 07:16:32AM -0400, Jon

Re: [ptxdist] problem configuring python3

On Tue, Jun 15, 2021 at 8:08 AM Michael Olbrich wrote: > On Tue, Jun 15, 2021 at 07:16:32AM -0400, Jon Ringle wrote: > > On Tue, Jun 15, 2021 at 2:11 AM Michael Olbrich < > m.olbr...@pengutronix.de> > > wrote: > > > > > On Mon, Jun 14, 2021 at 05:57:36PM -0

Re: [ptxdist] problem configuring python3

On Tue, Jun 15, 2021 at 2:11 AM Michael Olbrich wrote: > On Mon, Jun 14, 2021 at 05:57:36PM -0400, Jon Ringle wrote: > > It seems like I'm having a problem with python3.7m in sysroot-host trying > > to use the host libm. I'm not sure if the issue is with ptxdist or with &

[ptxdist] problem configuring python3

It seems like I'm having a problem with python3.7m in sysroot-host trying to use the host libm. I'm not sure if the issue is with ptxdist or with the docker container image I use for building the ptxdist bsp. --- target: python3.prepare --- checking for

[ptxdist] collections changed?

As I am updating bsp from 2020.10.0 to 2021.05.0, I noticed that the collections now remove every package that I had previously marked to build for the collection. How is this supposed to work now? -Jon ___ ptxdist mailing list ptxdist@pengutronix.de To

Re: [ptxdist] aclocal-1.15 is missing on your system

Please ignore. I had inadvertently removed several patches/*/autogen.sh symlinks in my build of ptxdist. On Thu, May 27, 2021 at 1:41 PM Jon Ringle wrote: > Anyone have suggestions on how to resolve this? > > > target: host

Re: [ptxdist] SHARED_GDB_VERSION is undefined or empty

On Thu, May 27, 2021 at 9:50 AM Roland Hieber wrote: > On Thu, May 27, 2021 at 09:45:04AM -0400, Jon Ringle wrote: > > I'm in the process of updating our bsp to 2021.05.0, and I'm running into > > this problem and I'm not sure how to fix this... > > > > /usr/local/lib

[ptxdist] aclocal-1.15 is missing on your system

Anyone have suggestions on how to resolve this? target: host-acl.compile make: Entering directory '/src/build/platform-ec2k/build-host/acl-2.2.53' CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh

[ptxdist] SHARED_GDB_VERSION is undefined or empty

I'm in the process of updating our bsp to 2021.05.0, and I'm running into this problem and I'm not sure how to fix this... /usr/local/lib/ptxdist-2021.05.1_GP/rules/gdbserver.make:18: *** SHARED_GDB_VERSION is undefined or empty. Stop. I see that it gets defined in gdb.make: SHARED_GDB_VERSION

Re: [ptxdist] systemctl daemon-reload fails

On Wed, Oct 28, 2020 at 3:59 AM Michael Olbrich wrote: > > On Wed, Oct 28, 2020 at 08:28:11AM +0100, Michael Olbrich wrote: > > On Wed, Oct 21, 2020 at 09:27:54AM +0200, Ladislav Michl wrote: > > > On Tue, Oct 20, 2020 at 08:57:27AM -0400, Jon Ringle wrote: > > > >

Re: [ptxdist] systemctl daemon-reload fails

On Tue, Oct 20, 2020 at 2:06 AM Ladislav Michl wrote: > > On Mon, Oct 19, 2020 at 02:32:49PM -0400, Jon Ringle wrote: > > I recently updated to ptxdist-2020.10.0 for running on our device that > > has 64MB or physical ram. > > With systemd-246.6 that is installed,

Re: [ptxdist] systemctl daemon-reload fails

On Mon, Oct 19, 2020 at 2:32 PM Jon Ringle wrote: > > I recently updated to ptxdist-2020.08.0 for running on our device that correction. I meant ptxdist-2020.10.0 > has 64MB or physical ram. > With systemd-246.6 that is installed,I'm finding that systemd > daemon-reload now fa

[ptxdist] systemctl daemon-reload fails

I recently updated to ptxdist-2020.08.0 for running on our device that has 64MB or physical ram. With systemd-246.6 that is installed,I'm finding that systemd daemon-reload now fails: $ sudo systemctl daemon-reload Failed to reload daemon: Refusing to reload, not enough space available on

Re: [ptxdist] install_copy_toolchain_lib: libnsl.so not found

On Wed, Oct 7, 2020 at 3:05 AM Michael Olbrich wrote: > > On Tue, Oct 06, 2020 at 10:33:00PM -0400, Jon Ringle wrote: > > On Tue, Oct 6, 2020 at 10:03 PM Jon Ringle wrote: > > > On Tue, Oct 6, 2020 at 9:54 PM Jon Ringle wrote: > > > > > > > >

Re: [ptxdist] install_copy_toolchain_lib: libnsl.so not found

On Tue, Oct 6, 2020 at 10:03 PM Jon Ringle wrote: > > On Tue, Oct 6, 2020 at 9:54 PM Jon Ringle wrote: > > > > I ran into this issue while updating our BSP to ptxdist-2020.09.0 with > > OSELAS.Toolchain-2020.08.0 that I'm not sure how to resolve. > > > [...] >

Re: [ptxdist] install_copy_toolchain_lib: libnsl.so not found

On Tue, Oct 6, 2020 at 9:54 PM Jon Ringle wrote: > > I ran into this issue while updating our BSP to ptxdist-2020.09.0 with > OSELAS.Toolchain-2020.08.0 that I'm not sure how to resolve. > [...] > lib - > /opt/OSELAS.Toolchain-2020.08.0/arm-v5te-linux-gnueabi/gcc-10.2.1-glibc-

[ptxdist] install_copy_toolchain_lib: libnsl.so not found

I ran into this issue while updating our BSP to ptxdist-2020.09.0 with OSELAS.Toolchain-2020.08.0 that I'm not sure how to resolve. Any ideas? Thanks, -Jon --- target: glibc.targetinstall --- install_init: preparing for image creation of

Re: [ptxdist] reproducible timestamps in ipkg package

On Mon, Apr 20, 2020 at 12:28 PM Jon Ringle wrote: > I am having an issue where the timestamps for the files in the ipkg have > the current timestamp instead of the reproducible timestamp coming from > SOURCE_DATE_EPOCH. > I added a debug log message to ptxd_install_fixup_timest

[ptxdist] reproducible timestamps in ipkg package

I am having an issue where the timestamps for the files in the ipkg have the current timestamp instead of the reproducible timestamp coming from SOURCE_DATE_EPOCH. I added a debug log message to ptxd_install_fixup_timestamps() found in scripts/lib/ptxd_make_xpkg_pkg.sh to show the timestamp being

Re: [ptxdist] [PATCH v3] git-ptx-patches: call git in a pristine environment

On Mon, Nov 18, 2019 at 4:32 AM Roland Hieber wrote: > > @@ -129,7 +144,7 @@ fi > GIT_EXTRA_ARGS="$GIT_EXTRA_ARGS --summary --stat=80" > > cat .ptxdist/series.0 > .ptxdist/series > -git format-patch -N $GIT_EXTRA_ARGS ${tagopt} -o .ptxdist/patches/ > ${range} | sed -e 's,^.ptxdist/patches/,,'

Re: [ptxdist] RPi3b+ boot sequence with DistroKit (barebox)

On Sat, Sep 7, 2019 at 1:42 AM Jon Ringle wrote: > > On Tue, Sep 3, 2019 at 9:53 AM Roland Hieber wrote: > >> On Sat, Aug 31, 2019 at 10:35:05PM -0400, Jon Ringle wrote: >> > B) If so, where should the overlays/ directory live...? >> >> If you put the

Re: [ptxdist] RPi3b+ boot sequence with DistroKit (barebox)

On Tue, Sep 3, 2019 at 9:53 AM Roland Hieber wrote: > On Sat, Aug 31, 2019 at 10:35:05PM -0400, Jon Ringle wrote: > > B) If so, where should the overlays/ directory live...? > > If you put the DTBOs into configs/platform-v7a/rpi-firmware/overlays/, > you can change configs/

[ptxdist] host-meson: No module named 'setuptools'

I'm working on updating our bsp from 2019.01 to 2019.07 and I'm running in to the following problem building host-meson: -- target: host-meson.compile -- Traceback (most recent call last): File "setup.py", line 25, in from setuptools import

[ptxdist] qt4.make leaks include/lib path in devpkg

In rules/qt4.make, there is: ``` ifdef PTXCONF_QT4_EXAMPLES QT4_DEVPKG := NO endif ``` This means that a qt4 dev package will be probably be created. The qt4.extract rule will create some mkspecs files that contain the absolute path for include and lib dirs. These mkspecs files get packaged

Re: [ptxdist] [PATCH] host-autotools-autoconf: fix m4 path

a correct dev package for host-autotools-autoconf with this? The dev package still has the absolute path to sysroot-host m4 in it from the build that created the dev package, but this is getting fixed up correctly now when the dev package is being used. Tested-by: Jon Ringle

Re: [ptxdist] [PATCH] kernel: rework prepare stage

. I've queued this for master, but I'm still waiting for some test results before pushing this. Tested with 'ssh localhost "cd $(pwd); ptxdist images"' Looks good. Tested-by: Jon Ringle ___ ptxdist mailing list ptxdist@pengutronix.de

Re: [ptxdist] strange permission behavior

On Wed, Feb 20, 2019 at 10:43 AM Michael Olbrich wrote: > On Wed, Feb 20, 2019 at 10:29:45AM -0500, Jon Ringle wrote: > > On Wed, Feb 20, 2019 at 10:20 AM Michael Olbrich < > m.olbr...@pengutronix.de> > > wrote: > > > On Wed, Feb 20, 2019 at 10:10:01AM -0500,

Re: [ptxdist] strange permission behavior

On Wed, Feb 20, 2019 at 10:20 AM Michael Olbrich wrote: > On Wed, Feb 20, 2019 at 10:10:01AM -0500, Jon Ringle wrote: > > On Wed, Feb 20, 2019 at 9:42 AM Michael Olbrich < > m.olbr...@pengutronix.de> > > wrote: > > > On Wed, Feb 20, 2019 at 09:09:18AM -0500, Jon

Re: [ptxdist] strange permission behavior

On Wed, Feb 20, 2019 at 9:42 AM Michael Olbrich wrote: > On Wed, Feb 20, 2019 at 09:09:18AM -0500, Jon Ringle wrote: > > On Wed, Feb 20, 2019 at 8:22 AM Ian Abbott wrote: > > > > > On 20/02/2019 13:17, Ian Abbott wrote: > > > > On 20/02/2019 00:59, Jon Ringl

Re: [ptxdist] strange permission behavior

On Wed, Feb 20, 2019 at 8:22 AM Ian Abbott wrote: > On 20/02/2019 13:17, Ian Abbott wrote: > > On 20/02/2019 00:59, Jon Ringle wrote: > >> I've got a strange permission problem when I build on our build server > >> that was recently updated from Ubuntu-14.04 to Ubu

[ptxdist] strange permission behavior

I've got a strange permission problem when I build on our build server that was recently updated from Ubuntu-14.04 to Ubuntu-16.04. On our Ubuntu-16.04 server, on most of the platform/packages/ subdirectories the packages are getting created with other having no permissions at all:

[ptxdist] host-autoconf: hardcoded path to m4

The host-autoconf.make package creates a *-dev.tar.gz package, but the host-autoconf-2.69/bin/auto4mte script install found in it contains a hardcoded path to m4 that results in a build failure for future builds that use the host-autoconf-2.69-arm-*-dev.tar.gz package: Line 90 of the autom4te in

Re: [ptxdist] [PATCH] systemd-239: Fix struct statx compilation on OSELAS.Toolchain-2018.12.0

On Fri, Feb 15, 2019 at 4:20 AM Michael Olbrich wrote: > On Wed, Feb 13, 2019 at 10:24:03AM -0500, j...@ringle.org wrote: > > From: Jon Ringle > > > > Add upstream patch: > https://github.com/systemd/systemd/commit/9c869d08d82c73f62ab3527567858ce4b0cf1257 > >

[ptxdist] Problems building kernel image with initramfs with no tty

I've recently updated to ptxdist-2019.01.0 and have noted some changes with my project that builds a kernel image with initramfs: 1) In rules/kernel.make, there is the following code: # # Don't keep the expanded path to INITRAMS_SOURCE in $(KERNEL_CONFIG), # because it contains local workdir

Re: [ptxdist] [PATCH 1/3] host-faketime: new package

On Thu, Oct 11, 2018 at 10:43 AM Roland Hieber wrote: > > Hmmm, we had a similar patch in August that added libfaketime as a > runtime dependency to PTXdist in order to detect changes to packages' > patch series: > > https://www.mail-archive.com/ptxdist@pengutronix.de/msg13198.html > > If we can

Re: [ptxdist] [PATCH v4 1/2] Add libfaketime as a core component of ptxdist for patchin support

On Wed, Aug 8, 2018 at 6:58 AM Jon Ringle wrote: > On Wed, Aug 8, 2018 at 5:50 AM Roland Hieber wrote: >> On Fri, Aug 03, 2018 at 11:44:55AM -0400, j...@ringle.org wrote: >> > From: Jon Ringle >> > >> > libfaketime will be used during patchin so that c

Re: [ptxdist] [PATCH v4 1/2] Add libfaketime as a core component of ptxdist for patchin support

On Wed, Aug 8, 2018 at 5:50 AM Roland Hieber wrote: > On Fri, Aug 03, 2018 at 11:44:55AM -0400, j...@ringle.org wrote: > > From: Jon Ringle > > > > libfaketime will be used during patchin so that committer timestamps > always > > have a fixed value and therefore m

Re: [ptxdist] local rule makefile include $(PTXDIST_TOPDIR)/rules/...

[A-Z_]*" and not the same as the one found in $(PTXDIST_TOPDIR)/rules/*.make file -Jon On Fri, Aug 3, 2018 at 4:25 AM Jon Ringle wrote: > > Hi, > > As a follow up to my patch "Detect changes in package patch series", > I'd like to be able to further this

Re: [ptxdist] [PATCH v3] Detect changes in package patch series

On Fri, Aug 3, 2018 at 4:51 AM Uwe Kleine-König < u.kleine-koe...@pengutronix.de> wrote: > On Fri, Aug 03, 2018 at 04:41:56AM -0400, j...@ringle.org wrote: > > From: Jon Ringle > > > > For a long time it has bothered me that if a package's patches were > change

Re: [ptxdist] [PATCH v2] Detect changes in package patch series

On Fri, Aug 3, 2018 at 4:20 AM Alm, Michael wrote: > > Hi Jon, > > looks very useful. Just a little question: Does this only work when using > ptxdist together with git? Correct. The workflow for this uses the git-ptx-patches script which means you would need to do the patchin of packages with

[ptxdist] local rule makefile include $(PTXDIST_TOPDIR)/rules/...

Hi, As a follow up to my patch "Detect changes in package patch series", I'd like to be able to further this by having the ability to maintain my own patch series for a package without having to be forced to also maintain the package's rules makefile as well. To try to achieve this I tried having

Re: [ptxdist] [PATCH] Detect changes in package patch series

On Fri, Aug 3, 2018 at 3:36 AM Jon Ringle wrote: > > On Fri, Aug 3, 2018 at 3:19 AM Uwe Kleine-König > wrote: > > > > Hello Jon, > > > > On Thu, Aug 02, 2018 at 09:49:59PM -0400, j...@ringle.org wrote: > > > diff --git a/scripts/git-ptx-patches b/s

Re: [ptxdist] [PATCH] Detect changes in package patch series

On Fri, Aug 3, 2018 at 3:19 AM Uwe Kleine-König wrote: > > Hello Jon, > > On Thu, Aug 02, 2018 at 09:49:59PM -0400, j...@ringle.org wrote: > > diff --git a/scripts/git-ptx-patches b/scripts/git-ptx-patches > > index f2568f9..738a4ac 100755 > > --- a/scripts/git-ptx-patches > > +++

Re: [ptxdist] [PATCH 3/3] host-systemd: Fix rpath space problem

On Tue, Jul 31, 2018 at 9:53 AM Michael Olbrich wrote: > > On Tue, Jul 31, 2018 at 09:30:22AM -0400, Jon Ringle wrote: > > On Tue, Jul 31, 2018 at 3:49 AM Michael Olbrich > > wrote: > > > > > > On Mon, Jul 30, 2018 at 12:58:09PM -0400, j...@ringle

Re: [ptxdist] [PATCH v2] initramfs-tools: Restore package

ramfs-tools) > > + @$(call install_fixup, initramfs-tools,PRIORITY,optional) > > + @$(call install_fixup, initramfs-tools,SECTION,base) > > + @$(call install_fixup, initramfs-tools,AUTHOR,"Jon Ringle > > ") > > + @$(call install_fixu

Re: [ptxdist] [PATCH] initramfs-tools: Restore package

On Tue, Jul 10, 2018 at 3:00 AM Michael Olbrich wrote: > > On Fri, Jul 06, 2018 at 10:27:46PM -0400, Jon Ringle wrote: > > On Tue, Jun 19, 2018 at 10:45 AM Michael Olbrich > > wrote: > > > > > > On Mon, Jun 18, 2018 at 08:09:20AM -0400, j...@ringle.or

Re: [ptxdist] [PATCH] glibc: optional install libatomic

On Mon, Jul 9, 2018 at 8:19 AM Denis OSTERLAND wrote: > > Signed-off-by: Denis Osterland > --- > rules/glibc.in | 6 ++ > rules/glibc.make | 4 > 2 files changed, 10 insertions(+) > > diff --git a/rules/glibc.in b/rules/glibc.in > index bd0f1db91..3e50ef455 100644 > ---

Re: [ptxdist] [PATCH] initramfs-tools: Restore package

On Tue, Jun 19, 2018 at 10:45 AM Michael Olbrich wrote: > > On Mon, Jun 18, 2018 at 08:09:20AM -0400, j...@ringle.org wrote: > > +if INITRAMFS_TOOLS > > + > > +config INITRAMFS_SPEC > > Is this spec stuff something you need? I actually missed this when I > removed all the other pieces, so I'd

[ptxdist] IMAGE_TGZ_LABEL

In commit bddcd2a1bfad90a1a1cbf250482f131774d141db, it removes the config option IMAGE_TGZ_LABEL. Removing this option, which adds a label to the tar image, breaks the firmware update for our board. Where would the proper place be to reintroduce this? Thanks, -Jon

Re: [ptxdist] initramfs

Sorry for the delay in response on this. My laptop died and spent a couple days rebuilding it and catching up on work before going on vacation... On Tue, Jun 19, 2018 at 10:31 AM Michael Olbrich wrote: > I'd still like to know a bit more about your use-case. I know very little > about what other

Re: [ptxdist] initramfs

On Mon, Jun 18, 2018 at 5:49 AM Michael Olbrich wrote: > > Hi, > > On Fri, Jun 15, 2018 at 12:37:11PM -0400, Jon Ringle wrote: > > In 4e8ea1703cad595f3136f0d48ae93de73a180c40 (remove obsolete and > > broken klibc/initramfs), I agree that klibc is broken and should be >

[ptxdist] kernel with initramfs image

Prior to ptxdist-2018.06.0 I was able to generate a linuximage with an embedded initramfs image within it. That is no longer working, and I'm not sure if this is because I haven't configured my ptxconfig properly for the new image generation code introduced in this new version of ptxdist, or if

[ptxdist] initramfs

In 4e8ea1703cad595f3136f0d48ae93de73a180c40 (remove obsolete and broken klibc/initramfs), I agree that klibc is broken and should be removed. However, I use initramfs. I have in the ptxconfig for building my kernel image: PTXCONF_INITMETHOD_INITRAMFS=y PTXCONF_INITRAMFS_TOOLS=y

Re: [ptxdist] missing libfakeroot.so

On Tue, Jun 12, 2018 at 3:56 PM Michael Olbrich wrote: > > On Tue, Jun 12, 2018 at 03:20:33PM -0400, Jon Ringle wrote: > > On Tue, Jun 12, 2018 at 9:39 AM Michael Olbrich > > wrote: > > > > > > On Tue, Jun 12, 2018 at 08:43:34AM -0400, Jon Ringle wrote: &g

Re: [ptxdist] missing libfakeroot.so

On Tue, Jun 12, 2018 at 9:39 AM Michael Olbrich wrote: > > On Tue, Jun 12, 2018 at 08:43:34AM -0400, Jon Ringle wrote: > > I'm running into the following problem building on our bamboo server. > > It complains about missing libfakeroot.so, but as you can see, target > > ho

[ptxdist] missing libfakeroot.so

I'm running into the following problem building on our bamboo server. It complains about missing libfakeroot.so, but as you can see, target host-fakeroot.install.post completes, which I presume should have installed libfakeroot.so under $(SYSROOT_HOST)? Any ideas? -Jon build 12-Jun-2018

Re: [ptxdist] [PATCH] libelf: version bump 0.170 -> 0.171

On Tue, Jun 5, 2018 at 3:34 PM, Jon Ringle wrote: > > > On Tue, Jun 5, 2018 at 3:04 PM, Alexander Dahl wrote: > >> Hei hei, >> >> On Tue, Jun 05, 2018 at 02:20:37PM -0400, Jon Ringle wrote: >> > The bump to 0.171 fixed the errors I was getting when build

Re: [ptxdist] [PATCH] libelf: version bump 0.170 -> 0.171

On Tue, Jun 5, 2018 at 3:04 PM, Alexander Dahl wrote: > Hei hei, > > On Tue, Jun 05, 2018 at 02:20:37PM -0400, Jon Ringle wrote: > > The bump to 0.171 fixed the errors I was getting when building 0.170, so > I > > think the patch is not needed > > I already saw y

Re: [ptxdist] [PATCH] libelf: version bump 0.170 -> 0.171

On Tue, Jun 5, 2018 at 2:05 PM, Alexander Dahl wrote: > Hello Jon, > > On Tue, Jun 05, 2018 at 01:18:06PM -0400, j...@ringle.org wrote: > > rules/libelf.make | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > There's a patch in patches/elfutils-0.170 you didn't cover. ;-) > Hi

Re: [ptxdist] [PATCH] libfastjson: version bump 0.99.4 -> 0.99.6

Please disregard this patch. I am sending a new one that bumps to the latest 0.99.8 -Jon On Tue, Jun 5, 2018 at 4:33 AM, wrote: > From: Jon Ringle > > Signed-off-by: Jon Ringle > --- > patches/{libfastjson-0.99.4 => libfastjson-0.99.6}/autogen.sh | 0 > r

Re: [ptxdist] [PATCH] cross-gdb: Make CROSS_GDB_WITHOUT_PYTHON an explicit "opt-out" option

On Tue, Feb 27, 2018 at 2:24 AM, Michael Olbrich <m.olbr...@pengutronix.de> wrote: > On Fri, Feb 23, 2018 at 09:41:45AM -0500, j...@ringle.org wrote: > > From: Jon Ringle <jrin...@gridpoint.com> > > > > python3 support in cross-gdb will be enabled by default u

Re: [ptxdist] gdb python support

> > > > > 4) rules/cross-gdb.make has the following, but I do not have > > > > CROSS_GDB_WITHOUT_PYTHON set at all in my environment: > > > > > > Are you using build_all_v2.mk or build_one.sh? Then > > > CROSS_GDB_WITHOUT_PYTHON is set to 'y' by default. > > > > > > > > Ok. I see that there now.

Re: [ptxdist] gdb python support

On Thu, Feb 22, 2018 at 3:34 PM, Michael Olbrich <m.olbr...@pengutronix.de> wrote: > Hi, > > On Thu, Feb 22, 2018 at 02:05:03PM -0500, Jon Ringle wrote: > > 3) I have `python-dev` package installed > > This should probably be python3-dev > > Ok > > 4)

[ptxdist] gdb python support

In building the OSELAS.Toolchain 2018.02.0 for arm-v5te, I noticed that the resulting cross-gdb didn't have python support in it. I'm a bit perplexed on how this is: ~/oselas/OSELAS.Toolchain-2018.02.0$ readelf -d

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

I built the arm-v5te toolchain, and it built: oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo14.04+1_amd64.deb But on https://debian.pengutronix.de/debian/pool/main/o/oselas.toolchain/ I see:

Re: [ptxdist] [PATCH support/ptxdist-2017.05.x_GP v3] ptxd_make_world_compile.sh: conditionally redirect stderr>stdout

Ping... On Wed, May 24, 2017 at 10:39 PM, <j...@ringle.org> wrote: > From: Jon Ringle <jrin...@gridpoint.com> > > I discovered after updating to a new version of ptxdist that all of my > compile output including errors/warnings are now all going to stdout > instead o

Re: [ptxdist] [PATCH support/ptxdist-2017.05.x_GP v2 1/2] f2fs-tools: version bump 1.6.1 -> 1.8.0

Ping... On Wed, May 24, 2017 at 10:39 PM, <j...@ringle.org> wrote: > From: Jon Ringle <jrin...@gridpoint.com> > > Signed-off-by: Jon Ringle <jrin...@gridpoint.com> > --- > patches/f2fs-tools-1.6.1/autogen.sh | 1 - > patches/f2fs-tools-1.8.0/autog

Re: [ptxdist] ptxdist compile redirects stderr to stdout

On Thu, 1 Dec 2016, Michael Olbrich wrote: > Hi, > > On Wed, Nov 30, 2016 at 03:46:14AM -0500, Jon Ringle wrote: > > I found that this is being caused by commit > > 30b9267e35eea1c2edb4da0231a428bfa25b6766 > > > > Is there a way that the stderr to std

[ptxdist] ptxdist compile redirects stderr to stdout

I discovered after updating to a new version of ptxdist that all of my compile output including errors/warnings are now all going to stdout instead of having the errors/warning going to stderr. This is causing some problem when I use qtcreator as my IDE because qtcreator will only filter

Re: [ptxdist] [PATCH 0/6] OSELAS.Toolchain host tool version bumps

On Sun, Dec 13, 2015 at 2:37 PM, Robert Schwebel wrote: > Thanks for your patches, but Michael is already testing the toolchain > for the new december release. Please stay tuned, a release is already > being prepared based on the latest-and-greatest. What is the status

Re: [ptxdist] [PATCH] glib: Patch glib-2.0.pc.in to use '-isystem dir' rather than '-Idir'

On Fri, Oct 30, 2015 at 6:22 AM, Michael Olbrich <m.olbr...@pengutronix.de> wrote: > On Fri, Oct 16, 2015 at 10:02:59AM -0400, Jon Ringle wrote: >> Ping... >> >> On Sat, Oct 3, 2015 at 9:11 AM, Jon Ringle <j...@ringle.org> wrote: >> > On Sat, Oc

Re: [ptxdist] [PATCH] glib: Patch glib-2.0.pc.in to use '-isystem dir' rather than '-Idir'

Ping... On Sat, Oct 3, 2015 at 9:11 AM, Jon Ringle <j...@ringle.org> wrote: > On Sat, Oct 3, 2015 at 4:56 AM, Marc Kleine-Budde <m...@pengutronix.de> wrote: >> On 10/03/2015 05:06 AM, j...@ringle.org wrote: >>> From: Jon Ringle <jrin...@gridpoint.com> >

Re: [ptxdist] [PATCH] glib: Patch glib-2.0.pc.in to use '-isystem dir' rather than '-Idir'

On Sat, Oct 3, 2015 at 4:56 AM, Marc Kleine-Budde <m...@pengutronix.de> wrote: > On 10/03/2015 05:06 AM, j...@ringle.org wrote: >> From: Jon Ringle <jrin...@gridpoint.com> >> >> When ptxdist did a bump to glib-2.44.0, a project that uses glib and builds >> w

Re: [ptxdist] [PATCH 1/2] strognswan: version bump 5.2.2 - 5.3.2

typo in comment subject: strognswan = strongswan -- ptxdist mailing list ptxdist@pengutronix.de

[ptxdist] Error building bash-4.3.33

I'm running into the following error while building bash-4.3.33, any ideas as to what might be missing? Jon target: bash.compile make[1]: Entering directory `/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/build-target/bash-4.3.30' rm

Re: [ptxdist] Error building bash-4.3.33

On Fri, Apr 17, 2015 at 7:55 AM, Michael Olbrich m.olbr...@pengutronix.de wrote: On Fri, Apr 17, 2015 at 07:37:44AM -0400, Jon Ringle wrote: I'm running into the following error while building bash-4.3.33, any ideas as to what might be missing? [...] /usr/src/local/bash/bash-4.3-patched

Re: [ptxdist] Problems building libnl3

On Thu, Mar 26, 2015 at 7:59 AM, Jon Ringle j...@ringle.org wrote: Removing both host-{m4,flex}-*-dev.tar.gz seemed to do the trick... I believe that I found the crux of the issue. We have a bamboo build server running Ubuntu-10.04 that generated the *-dev.tar.gz files. We are in the process

Re: [ptxdist] Problems building libnl3

On Thu, Mar 26, 2015 at 5:23 AM, Michael Olbrich m.olbr...@pengutronix.de wrote: On Wed, Mar 25, 2015 at 09:21:32AM -0400, Jon Ringle wrote: On Tue, Jan 27, 2015 at 11:22 PM, Jon Ringle j...@ringle.org wrote: On Mon, Jan 26, 2015 at 8:44 AM, Michael Olbrich m.olbr...@pengutronix.de wrote

Re: [ptxdist] Problems building libnl3

On Thu, Mar 26, 2015 at 6:53 AM, Jon Ringle j...@ringle.org wrote: On Thu, Mar 26, 2015 at 5:23 AM, Michael Olbrich m.olbr...@pengutronix.de wrote: On Wed, Mar 25, 2015 at 09:21:32AM -0400, Jon Ringle wrote: On Tue, Jan 27, 2015 at 11:22 PM, Jon Ringle j...@ringle.org wrote: On Mon, Jan 26

Re: [ptxdist] Problems building libnl3

On Tue, Jan 27, 2015 at 11:22 PM, Jon Ringle j...@ringle.org wrote: On Mon, Jan 26, 2015 at 8:44 AM, Michael Olbrich m.olbr...@pengutronix.de wrote: Hi, On Wed, Jan 21, 2015 at 02:22:26PM -0500, Jon Ringle wrote: After updating to ptxdist-2015-01.0, I am having a problem build libnl3. I

[ptxdist] libnl3 build problem: flex: fatal internal error, exec failed

I just updated to ptxdist-2015.03.0 as a test, and I am running into the following error with libnl3: -- target: libnl3.compile -- make[1]: Entering directory `/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/build-target/libnl-3.2.25'

Re: [ptxdist] (no subject)

On Sat, Feb 21, 2015 at 6:07 PM, Rüdiger, Christoph christoph.ruedi...@thyssenkrupp.com wrote: Hello, I'm trying to use ptxdist on a Mac OS X system to get rid of the Linux VM just for compiling things. Here is the thing I stumbled upon because I don't get the intention and therefore

Re: [ptxdist] Problems building libnl3

On Mon, Jan 26, 2015 at 8:44 AM, Michael Olbrich m.olbr...@pengutronix.de wrote: Hi, On Wed, Jan 21, 2015 at 02:22:26PM -0500, Jon Ringle wrote: After updating to ptxdist-2015-01.0, I am having a problem build libnl3. I tried rebuilding host-flex, hoping this might do the trick

[ptxdist] Problems building libnl3

After updating to ptxdist-2015-01.0, I am having a problem build libnl3. I tried rebuilding host-flex, hoping this might do the trick, but it did not help. Any ideas? Jon -- target: libnl3.compile -- make[1]: Entering directory

Re: [ptxdist] targetinstall fails

On Wed, Dec 31, 2014 at 7:55 AM, Michael Olbrich m.olbr...@pengutronix.de wrote: On Wed, Dec 31, 2014 at 01:57:17AM -0500, Jon Ringle wrote: Changing the /bin/sh link to point to bash instead of dash fixed this for me On Tue, Dec 30, 2014 at 2:02 PM, Jon Ringle j...@ringle.org wrote

Re: [ptxdist] targetinstall fails

On Fri, Jan 2, 2015 at 9:28 AM, Jon Ringle j...@ringle.org wrote: On Wed, Dec 31, 2014 at 7:55 AM, Michael Olbrich m.olbr...@pengutronix.de wrote: On Wed, Dec 31, 2014 at 01:57:17AM -0500, Jon Ringle wrote: Changing the /bin/sh link to point to bash instead of dash fixed this for me

[ptxdist] targetinstall fails

I'm setting up a new machine with Ubuntu-14.04 where I'll be doing ptxdist builds. I'm running into a problem where the targetinstall step fails on all packages with something like the following (I added 'set -x' to the fakeroot script for debugging purposes): ---

  1   2   3   >