Dears,
I just build the yocto image and within local.conf I got
IMAGE_INSTALL_append = "e2fsprogs"
but unfortunately I do not get resize2fs utility installed. I do not not
why?
this how e2fsprogs_1.42.9.bb looks like
require e2fsprogs.inc
SRC_URI += "file://acinclude.m4 \
file:
Hello Jason,
I'm interested in your code + BitBake recipe to be able to *automatically
resize on first boot*.
Thank you.
Peter
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
This is more likely to work:
bitbake-layers show-recipes gcc
Cheers,
Paul
On Wed, 12 Oct 2016 21:19:59 Sandeep G.R wrote:
> Hi Vijay,
>
> You can run *"bitbake-layers show-recipes | grep gcc-source"* to know more
> on supported toolchain versions.
>
> On Wed, Oct 12, 2016 at 11:55 AM, Vijaya
Hi Vijay,
You can run *"bitbake-layers show-recipes | grep gcc-source"* to know more
on supported toolchain versions.
On Wed, Oct 12, 2016 at 11:55 AM, Vijayakumar Badiger <
vijayakuma...@gmail.com> wrote:
> Thanks Paul, appreciate your reply.
>
> Cheers,
> Vijay
>
>
> On Mon, Oct 10, 2016 at 6:
On Thu, Oct 06, 2016 at 09:39:46PM -0700, Khem Raj wrote:
> Signed-off-by: Khem Raj
> ---
> .../0001-fix-dtbo-rules.patch | 44
> ++
> ...835-camera-fix-compilation-warning-werror.patch | 35 +
> recipes-kernel/linux/linux-raspberrypi_4.8.
I wanted to add that it's specifically the glibc development packages which
have this fpu_control.h file conflict.
IMAGE_INSTALL += "glibc-dev"
IMAGE_INSTALL += "lib32-glibc-dev"
-Glenn
From: Stroz, Glenn
Sent: Tuesday, October 11, 2016 4:54 PM
To: 'yocto@yoctoproject.org'
Subject: Conflict be
RM_OLD_IMAGE has been removed as it's now the default behaviour.
Signed-off-by: Joshua Lock
---
documentation/ref-manual/ref-variables.xml | 22 --
1 file changed, 22 deletions(-)
diff --git a/documentation/ref-manual/ref-variables.xml
b/documentation/ref-manual/ref-variabl
On 10/12/2016 05:51 AM, Beth 'pidge' Flanagan wrote:
> On Mon, 2016-10-10 at 09:54 -0500, Aníbal Limón wrote:
>> From: Monserrat Sedeno
>>
>> As part of the process to set new OS distribution as supported on
>> Yoctoc Project
>> a new patch was created with the list of build sets that should be
Thanks Paul, appreciate your reply.
Cheers,
Vijay
On Mon, Oct 10, 2016 at 6:24 PM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:
> Hi Vijay,
>
> On Mon, 10 Oct 2016 17:44:13 Vijayakumar Badiger wrote:
> > Please can some one tell me the tool chain versions supported on the
> latest
> >
On Wed, Oct 12, 2016 at 4:08 AM, Patrick Ohly
wrote:
> On Wed, 2016-10-12 at 12:58 +0300, Mircea Gliga wrote:
> > According to the docs here
> > http://www.yoctoproject.org/docs/2.1.1/mega-manual/mega-
> manual.html#structure-your-layers
> > one can specify variables that are machine specific, eg
On Wed, 2016-10-12 at 07:28 -0700, Bill Randle wrote:
> Hi Robert,
>
> Then "normal" method to send patches is via direct insertion into the
> email, rather than an attachment (see git-send-email). Also, it is
> missing a commit comment as the first text in the patch file.
> Otherwise, it looks go
On Mon, 2016-10-10 at 01:44 -0500, gm...@reliableembeddedsystems.com
wrote:
>
A few notes (not picking on this patch but it does point out some
design failures and I want to at least get this on folks radar).
I've been unhappy with how DeployArtifacts work for sometime.
Long ago, when I wrote
On Monday, October 10, 2016 12:23:07 PM EDT alfonso wrote:
> Hello everyone,
>
> I'm trying to integrate the testing of the resulting yocto images using
> Linaro's LAVA project.
>
> For now I am only using qemux86 images.
>
> Now, I am quite a newbie in both projects and maybe in general on the
Hi Robert,
Then "normal" method to send patches is via direct insertion into the
email, rather than an attachment (see git-send-email). Also, it is
missing a commit comment as the first text in the patch file.
Otherwise, it looks good to me now.
-Bill
2016-10-09 23:44 GMT-07:00 :
>
--
On Wed, 2016-10-12 at 12:58 +0300, Mircea Gliga wrote:
> According to the docs here
> http://www.yoctoproject.org/docs/2.1.1/mega-manual/mega-manual.html#structure-your-layers
>
> one can specify variables that are machine specific, eg
> KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb". I can't f
On Mon, 2016-10-10 at 09:54 -0500, Aníbal Limón wrote:
> From: Monserrat Sedeno
>
> As part of the process to set new OS distribution as supported on
> Yoctoc Project
> a new patch was created with the list of build sets that should be
> executed.
>
> Detailed information:
> https://wiki.yoctopr
According to the docs here
http://www.yoctoproject.org/docs/2.1.1/mega-manual/mega-manual.html#structure-your-layers
one can specify variables that are machine specific, eg
KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb". I can't find a reference
on how to create a task specific only for a certa
Hello Yocto.
I recently encountered following issue with Python module cross-build.
(On Yocto 2.0 based build system, using distutils.bbclass)
http://bugs.python.org/issue28421
Firstly I believed it is a Python issue, but further looked into, Yocto build
environment has some cutomization causin
On Wed, 2016-10-12 at 08:07 +, Poky Build User wrote:
> A release candidate build for yocto-2.2.rc1 is now available at:
>
>
> http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2.rc1
>
>
> Please begin QA on this build as soon as possible.
This isn't a useful QA target a
On Wed, 2016-10-12 at 08:07 +, Poky Build User wrote:
> A release candidate build for yocto-2.2.rc1 is now available at:
>
>
> http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2.rc1
>
>
> Please begin QA on this build as soon as possible.
This isn't a useful QA target as not ev
A release candidate build for yocto-2.2.rc1 is now available at:
http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2.rc1
Please begin QA on this build as soon as possible.
Build hash information:
meta-qt4 : fc9b050569e94b5176bed28b69ef28514e4e4553
meta-intel : 9052773016727a9398
21 matches
Mail list logo
