From: Oliver Graute <oliver.graute@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: yocto jethro failed on gettext-native
Date: Fri, 27 Apr 2018 08:19:32 +0200 [thread overview]
Message-ID: <20180427061932.GB9349@graute-opti> (raw)
In-Reply-To: <CAGAf8LwkCDyzkej_c31EjtxXBDP+dqx5ihMCwuBH5CDP5X5T4w@mail.gmail.com>
On 26/04/18, Zoran Stojsavljevic wrote:
> > I deleted all the build-imx6ulevk folder and build everything from
> > scratch with only one thread, waited a few hours for compilation and now
> > its working ;)
>
> Still, I am struggling to understand why??? What is the requirement
> behind this ask?
The requirement was just get our older yocto (jethro) build running on a
PC of a different developer. Often developers have their own flavor of
Ubuntu releases and they update to newer versions while they still
develop on yocto releases which is much older. Because that yocto
release is currently in the field by our costumer. Our product cycle is
not so fast to use the newest yocto releases. We started to develop when
jethro was up to date.
We compiled single threaded just because his PC is a bit unstable on
high load. And it crashed a few times on parallel makes. I know that
this is not ideal for yocto development.
>
> As we see, it is much longer (one thread only) than on 14.04!?
its takes much longer then with settings
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"
> Could you, please, do it on Ubuntu 17.04, or 17.10 (i bet, you
> can't)??? And why, after all???
currently not im using only Ubuntu LTS Releases.
Perhaps I will try 18.04 LTS which released yesterday ;)
Best regards,
Oliver
next prev parent reply other threads:[~2018-04-27 6:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 15:03 yocto jethro failed on gettext-native Oliver Graute
2018-04-25 17:49 ` Zoran Stojsavljevic
[not found] ` <CAEv37YsacVBmZXtShCij9OxkXmQpUX92QnS=tg_ESO_0NkT3ow@mail.gmail.com>
2018-04-25 18:27 ` Zoran Stojsavljevic
2018-04-25 19:36 ` Oliver Graute
2018-04-25 19:50 ` Burton, Ross
2018-04-25 20:49 ` Randy MacLeod
2018-04-25 20:55 ` Zoran Stojsavljevic
2018-04-25 20:58 ` Zoran Stojsavljevic
2018-05-02 20:36 ` Paul Barker
2018-05-03 3:29 ` Zoran Stojsavljevic
2018-04-26 4:07 ` Andre McCurdy
2018-04-26 15:53 ` Oliver Graute
2018-04-26 17:33 ` Zoran Stojsavljevic
2018-04-27 6:19 ` Oliver Graute [this message]
2018-04-27 9:25 ` Zoran Stojsavljevic
2018-04-27 12:04 ` Philip Balister
2018-04-27 13:27 ` Zoran Stojsavljevic
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=20180427061932.GB9349@graute-opti \
--to=oliver.graute@gmail.com \
--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.