Hi #PTXdist,
I'm currently facing the issue that all my PTXdist builds fail in
'rootfs.make' during the creation of the /dev/null device node:
--( ... )--
install directory:
dir=/dev
owner=0
group=0
permissions=0755
install device node:
owner
Am Thu, 30 Sep 2021 12:44:34 +0200
schrieb Michael Olbrich :
> On Thu, Sep 30, 2021 at 07:59:45AM +0000, Koch, Alexander wrote:
> > Hi #PTXdist,
> >
> > I'm currently facing the issue that all my PTXdist builds fail in
> > 'rootfs.make' during
Am Thu, 30 Sep 2021 12:00:50 +
schrieb "Koch, Alexander" :
> Am Thu, 30 Sep 2021 12:44:34 +0200
> schrieb Michael Olbrich :
>
> > On Thu, Sep 30, 2021 at 07:59:45AM +, Koch, Alexander wrote:
> > > Hi #PTXdist,
> > >
> > > I'm c
Hi,
I just hat to a very strange problem building qt4 4.8.7 for ARMv7 using
OSELAS-2018.12.0 as target compiler and gcc-9.1.0 x64 as host compiler
and thought I'd share the knowledge.
The 'compile' step of qt4 yields all kinds of strange errors, most
noticeably these:
platform-pv3/build-targ
---
.../0001-Fix-for-gawk-5.0.patch | 159 ++
patches/libgpg-error-1.32/series | 1 +
2 files changed, 160 insertions(+)
create mode 100644 patches/libgpg-error-1.32/0001-Fix-for-gawk-5.0.patch
create mode 100644 patches/libgpg-error-1.32/series
Hi,
I stumbled upon this as well, when upgrading glibc under Arch.
So to clarify, do we just need to wait until the patch mentioned by Alex in [0]
gets included in an updated glibc package, or is there a proper way to make
PTXdist (or better `genimage`) work again under Arch?
Best regards,
Ale
Hi all,
I'd like to build an image for an x86 box (Intel Atom Z510). Coming from
the official documentation quickstart I found the OSELAS Generic BSP
[1], which seems to be based on ptxdist-2014.07.0.
I tried migrating it to ptxdist-2016.04.0 but multiple components (e.g.
klibc) fail to build.
I
Hi Alex,
>> Is there anything newer to act as a starting point for creating x86
>> images with recent PTXdist versions?
>>
> The DistroKit [0].
Thanks for the hint. I had had a quick look at this before, but found
only the platform definitions for arm7a and rpi, and therefore dropped it.
>
>> An