Dears,
I have built under Ubuntu/Linux 14.04 an Yocto image *imx-morty* for
i.MX6QP with *bitbake fsl-image-qt5*. Now I want to generate the
cross-toolchain for this image as follows
root@02849625e4d5:/home/root/fsl-morty-bsp/build-x11/tmp/deploy/sdk# sh
fsl-imx-x11-glibc-x86_64-fsl-image-qt5-cor
Hello,
I see that there are 2 source directory for linux, and I can't see any
difference between them:
build/tmp/work-shared/lec-imx6/kernel-source/
build/tmp/work/lec_imx6-poky-linux-gnueabi/linux-imx/4.1.15-r0/git
Why do we need two , are both used ?
Regards,
Ran
--
Hi Martyn,
On Mon, 13 Nov 2017 19:19:47 +
Martyn Welch wrote:
> Sometimes we wish to ensure that packages don't install files or
> directories somewhere that may prove detrimental to the operation of the
> system. For example, this may be the case if files are placed in a
> directory that is
On 11/14/2017 02:47 PM, Alexander Kanavin wrote:
I think this situation is an image configuration problem, not a package
qa problem. If a package wants to install something in a location that
is deemed inappropriate by the local config, there's a reason behind it,
the fix may not be easy to de
On 11/13/2017 09:19 PM, Martyn Welch wrote:
Sometimes we wish to ensure that packages don't install files or
directories somewhere that may prove detrimental to the operation of the
system. For example, this may be the case if files are placed in a
directory that is utilised as a mount point at r
Hi,
/dev/null in pseudo with -r does not work as expected (see commands below).
For example fakechroot behaves as I expected (see below). Can I obtain
similar behavior like fakechroot using pseudo?
Thank you.
Pavlina
--
root# /root/ps_dir/ps3/pseudo/bin/pseud
