The compilation of features.egl was failing because wayland-client.h was
not found in Yocto 2.5 sysroot of QTbase. In yocto 2.2, the sysroot was
common so qtbase was able to find this header even without dependencies.
Adding DEPENDS=wayland in qtbase recipe is compiling qtbase and qtwayland
Hi,
I am building an image on Ubuntu 18.04 host, I got following error:
unable to execute 'x86_64-linux-gnu-gcc': No such file or directory
| error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
I can see the x86_64-linux-gnu-gcc is available, but why it failed to find it?
$ which
> squashfs-xz (by poky) works,
> squashfs_xz_ubi (custom type) also works
To clarify, squashfs_xz_ubi was named squashfs-xz-ubi before,
I renamed it in order to try to avoid using "-".
--
___
yocto mailing list
yocto@yoctoproject.org
> I think there is some translation code somewhere which probably
> confuses things more as some bits have - and some have _. Does the
> squashfs_xz image type actually work?
There is no squashfs_xz image type.
squashfs-xz (by poky) works,
squashfs_xz_ubi (custom type) also works,
but needs to
This reverts commit e6e9d6e290028b0a6b83b563fad9fafa7f1d515e.
It was a 4.19.31 backport of commit 6ea183d60c46 ("mm: handle
lru_add_drain_all for UP properly"). In summary, what that did
was to fix a possible harmless WARN_ON on non-SMP, introduced at
commit 4d43d395fed1 ("workqueue: Try to
On Mon, 2019-04-15 at 21:43 +0700, Eric Grunt wrote:
> > Notice how the function names for squashfs are:
> >
> > do_image_squashfs_xz
> >
> > not
> >
> > do_image_squashfs-xz
> >
> > This is because shell functions/variables can't have "-" in their
> > name.
> > You need to change to us
> Notice how the function names for squashfs are:
>
> do_image_squashfs_xz
>
> not
>
> do_image_squashfs-xz
>
> This is because shell functions/variables can't have "-" in their name.
> You need to change to us IMAGE_CMD_squashfs_xz_ubi.
I tried to basically change all "-" in the fs and variable
Hi all,
I stumbled into an file synchronization problem, and I am curious if there are
more people using Yocto and ubifs/xfs/similar that have an interest of "fsync
before rename"?
When trying to atomically update a file a common flow is "create copy, edit
copy, rename copy->original", but
On Sun, 2019-04-14 at 23:48 +, pokybuild@centos7-ty-1.localdomain
wrote:
> A build flagged for QA (yocto-2.7.rc2) was completed on the
> autobuilder and is available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-2.7.rc2
>
>
> Build hash information:
>
> bitbake:
On Mon, 2019-04-15 at 08:27 +, pokybu...@fedora29-ty-1.yocto.io
wrote:
> A build flagged for QA (yocto-2.6.2.rc4) was completed on the
> autobuilder and is available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-2.6.2.rc4
>
>
> Build hash information:
>
> bitbake:
A build flagged for QA (yocto-2.6.2.rc4) was completed on the autobuilder and
is available at:
https://autobuilder.yocto.io/pub/releases/yocto-2.6.2.rc4
Build hash information:
bitbake: 7c1eb51d1e8a4c5f39bf9dddf05fb0b3598da72b
meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575
From: Richard Purdie
Currently systemtap fails to operate correctly on armv7 systems such as
beaglebone and
soon, qemuarm.
root@qemuarm:/usr/src/kernel# env -uARCH -uKBUILD_EXTMOD -uCROSS_COMPILE
-uKBUILD_IMAGE -uKCONFIG_CONFIG -uINSTALL_PATH -uLD_LIBRARY_PATH
12 matches
Mail list logo
