All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: jags gediya <jags.gediya@gmail.com>, <yocto@yoctoproject.org>,
	<meta-freescale@yoctoproject.org>
Subject: Re: Yocto build is taking too long time in kernel do_package and do_populate_sysroots
Date: Mon, 14 Jul 2014 14:27:37 -0400	[thread overview]
Message-ID: <53C42119.8000406@windriver.com> (raw)
In-Reply-To: <CAP3RZojz+v3uDix=a2XaAYhO36BCgVN7XoWr700To5HmCTjmyA@mail.gmail.com>

On 14-07-14 11:20 AM, jags gediya wrote:
> I am a newbie to yocto. For the purpose of check in code on svn, I
> have deleted all .git, .gitignore and .repo file from yocto before
> built. Then i have checked out that code from svn and started the
> yocto built.
>
> But my compilation used to stop at below point for more than an hour.

Depending on the speed of your machine, the disk, memory, etc .. yes,
those tasks can take a long time.

We've been working on improving kernel build and packaging time for
several releases now, and are still continuing in the upcoming
1.7 release.

The sheer amount of files, i/o and packaging required for the kernel
build, sysroot, kernel modules and packages simply takes time.

For incremental development, and testing workflow. Look into only
running the single task you need (i.e. just compile), or look at using
"externalsrc" support. Both those options will significant speed up
your iterative development time.

Bruce

>
> Currently 2 running tasks (1771 of 1777):
>      0: linux-imx-3.10.17-r0 do_package (pid 4011)
>      1: linux-imx-3.10.17-r0 do_populate_sysroot (pid 19696)
> I am building the core-image-minimal for imx6sl evk.
>
> Some modification i have done for the kernel and u-boot. I am not
> taking kernel and u-boot from the git. Instead i have changed the
> SRC_URI, and i have given there the path for kernel and u-boot to take
> it from local system.
>
> Things i have modified as per below.
> originally linux-imx.inc was having,
>
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
>
> inherit kernel
>
> # Put a local version until we have a true SRCREV to point to
> LOCALVERSION ?= "+yocto"
> SCMVERSION ?= "y"
>
> SRC_URI = "git://git.freescale.com/imx/linux-2.6-imx.git;branch=${SRCBRANCH} \
>             file://defconfig \
> "
>
> S = "${WORKDIR}/git"
>
> I have changed it to,
>
> #LICENSE = "GPLv2"
> #LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> LICENSE = "CLOSED"
>
> inherit kernel
>
> SRC_URI = "file://${BSPDIR}/kernel \
>             file://defconfig \
> "
> S = "${BSPDIR}/kernel"
>
> Can anyone point me if i have done any wrong configuration.
> PS: Before chevk in on svn, Kernel compilation was taking that much
> long time while building images.
>
> Thanks,
> Jags
>



WARNING: multiple messages have this Message-ID (diff)
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: jags gediya <jags.gediya@gmail.com>, <yocto@yoctoproject.org>,
	<meta-freescale@yoctoproject.org>
Subject: Re: [yocto] Yocto build is taking too long time in kernel do_package and do_populate_sysroots
Date: Mon, 14 Jul 2014 14:27:37 -0400	[thread overview]
Message-ID: <53C42119.8000406@windriver.com> (raw)
In-Reply-To: <CAP3RZojz+v3uDix=a2XaAYhO36BCgVN7XoWr700To5HmCTjmyA@mail.gmail.com>

On 14-07-14 11:20 AM, jags gediya wrote:
> I am a newbie to yocto. For the purpose of check in code on svn, I
> have deleted all .git, .gitignore and .repo file from yocto before
> built. Then i have checked out that code from svn and started the
> yocto built.
>
> But my compilation used to stop at below point for more than an hour.

Depending on the speed of your machine, the disk, memory, etc .. yes,
those tasks can take a long time.

We've been working on improving kernel build and packaging time for
several releases now, and are still continuing in the upcoming
1.7 release.

The sheer amount of files, i/o and packaging required for the kernel
build, sysroot, kernel modules and packages simply takes time.

For incremental development, and testing workflow. Look into only
running the single task you need (i.e. just compile), or look at using
"externalsrc" support. Both those options will significant speed up
your iterative development time.

Bruce

>
> Currently 2 running tasks (1771 of 1777):
>      0: linux-imx-3.10.17-r0 do_package (pid 4011)
>      1: linux-imx-3.10.17-r0 do_populate_sysroot (pid 19696)
> I am building the core-image-minimal for imx6sl evk.
>
> Some modification i have done for the kernel and u-boot. I am not
> taking kernel and u-boot from the git. Instead i have changed the
> SRC_URI, and i have given there the path for kernel and u-boot to take
> it from local system.
>
> Things i have modified as per below.
> originally linux-imx.inc was having,
>
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
>
> inherit kernel
>
> # Put a local version until we have a true SRCREV to point to
> LOCALVERSION ?= "+yocto"
> SCMVERSION ?= "y"
>
> SRC_URI = "git://git.freescale.com/imx/linux-2.6-imx.git;branch=${SRCBRANCH} \
>             file://defconfig \
> "
>
> S = "${WORKDIR}/git"
>
> I have changed it to,
>
> #LICENSE = "GPLv2"
> #LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> LICENSE = "CLOSED"
>
> inherit kernel
>
> SRC_URI = "file://${BSPDIR}/kernel \
>             file://defconfig \
> "
> S = "${BSPDIR}/kernel"
>
> Can anyone point me if i have done any wrong configuration.
> PS: Before chevk in on svn, Kernel compilation was taking that much
> long time while building images.
>
> Thanks,
> Jags
>



  reply	other threads:[~2014-07-14 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 15:20 Yocto build is taking too long time in kernel do_package and do_populate_sysroots jags gediya
2014-07-14 18:27 ` Bruce Ashfield [this message]
2014-07-14 18:27   ` [yocto] " Bruce Ashfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53C42119.8000406@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=jags.gediya@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.