From: "Kévin THIERRY" <kevin.thierry@open.eurogiciel.org>
To: Alex J Lennon <ajlennon@dynamicdevices.co.uk>,
ronan <ronan.lemartret@open.eurogiciel.org>
Cc: yocto@yoctoproject.org, general@lists.tizen.org
Subject: Re: [Tizen General] Build Tizen with yocto work-flow
Date: Mon, 04 Aug 2014 09:52:50 +0200 [thread overview]
Message-ID: <53DF3BD2.6000601@open.eurogiciel.org> (raw)
In-Reply-To: <53DD053A.9060902@dynamicdevices.co.uk>
On 02/08/2014 17:35, Alex J Lennon wrote:
> On 01/08/2014 17:36, Alex J Lennon wrote:
>> On 01/08/2014 16:38, Alex J Lennon wrote:
>>>> I don't know either but I think it's best to be compliant with both
>>>> bash and dash, I will try to correct those issues in order to be
>>>> dash-compliant. Thanks a lot for the feedback ;)
>>> No problem Kévin. I'm glad you feel it is of some use. I'm getting other
>>> recipes failing now with bash. What I'll probably do is let it run to
>>> completion with bitbake -k and collate the failures.
>>>
>>> Hopefully that'll be some useful feedback in terms of a build on Ubuntu
>>>
>>> Cheers,
>>>
>>> Alex
>>>
> Kévin,
>
> I made some progress with a USB installation of Yocto Tizen and a VirtualBox disk.
That's good news ! Did you have to make some changes in meta-tizen ? If
so, could you send us your patches so we can integrate them ? Thanks !
>
> Both a Samsung laptop running from USB and a VirtualBox machine boot, but after mounting the root filesystem they go extremely slowly.
>
> They get to "failed to get machine ID" and then it's taking a minute or two before new output appears. Then screen goes black and I don't appear to get any further.
>
> e.g. https://www.dropbox.com/sc/ckc84doykfnyvwp/AAAA7s_wocGh1PNUJ3tfIMBLa?n=17361870
>
>
We already encountered this issue in the past unfortunately we don't
know what causes that. We didn't get this issue recently so we are
unable to reproduce it. I'm wondering if it could be linked too the use
of a USB (we are not using USB anymore to test the images since it's not
very convenient). I will put an image on a USB stick and see how it goes.
If you have more ideas about what could cause this issue we would be
glad to know them.
Kevin
next prev parent reply other threads:[~2014-08-04 7:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 14:55 Build Tizen with yocto work-flow ronan
2014-07-31 15:40 ` [Tizen General] " Bob Summerwill
2014-08-01 9:56 ` Alex J Lennon
2014-08-01 10:03 ` ronan
2014-08-01 10:07 ` Alex J Lennon
2014-08-01 13:37 ` Ruud den Bekker
2014-08-01 14:13 ` [Tizen General] " Alex J Lennon
2014-08-01 14:38 ` Kévin THIERRY
2014-08-01 14:34 ` Alex J Lennon
2014-08-01 15:28 ` Alex J Lennon
2014-08-01 15:42 ` Kévin THIERRY
2014-08-01 15:38 ` Alex J Lennon
2014-08-01 16:36 ` Alex J Lennon
2014-08-02 15:35 ` Alex J Lennon
2014-08-02 19:52 ` Khem Raj
2014-08-02 20:04 ` Alex J Lennon
2014-08-04 7:52 ` Kévin THIERRY [this message]
2014-08-04 9:21 ` Alex J Lennon
2014-08-01 21:55 ` Richard Purdie
2014-08-02 9:35 ` Alex J Lennon
2014-08-04 7:37 ` Kévin THIERRY
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=53DF3BD2.6000601@open.eurogiciel.org \
--to=kevin.thierry@open.eurogiciel.org \
--cc=ajlennon@dynamicdevices.co.uk \
--cc=general@lists.tizen.org \
--cc=ronan.lemartret@open.eurogiciel.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.