From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: imx-bootlets build failure
Date: Sun, 22 Sep 2013 12:48:55 +0200 [thread overview]
Message-ID: <523ECB17.5010103@free-electrons.com> (raw)
In-Reply-To: <CAP9ODKo3BQLt+KY-s1iQDQzmf3ZnAohoBCBaTyEG1FsYLvk1uQ@mail.gmail.com>
On 21/09/2013 23:37, Otavio Salvador wrote:
> On Sat, Sep 21, 2013 at 4:48 AM, Alexandre Belloni
> <alexandre.belloni@free-electrons.com> wrote:
>> On 17/09/2013 16:38, Otavio Salvador wrote:
>>> Yes, this is weird indeed.
>>>
>>> This has been done using my autobuilder and it helps to spot some
>>> miss-use or weird things like that.
>>>
>>> So it uses same tmp directory for all builds and it helps to spot some
>>> inter-machine dependencies and wrong settings. I still not clear what
>>> might be causing this yet.
>>>
>> Ok, so I can reproduce it, using the following steps:
>>
>> MACHINE=cfa10036 . ./setup-environment build
>> bitbake core-image-minimal
>> rm -rf tmp/
>> cd ..
>> mv build/ build1
>> . ./setup-environment build1/
>> bitbake core-image-minimal
> I am attaching the patch that fixes the issue for me. Can you give it a try?
>
Working fine on my side !
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-09-22 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 14:03 imx-bootlets build failure Otavio Salvador
2013-09-17 14:24 ` Alexandre Belloni
2013-09-17 14:38 ` Otavio Salvador
2013-09-17 15:12 ` Eric Bénard
2013-09-21 7:48 ` Alexandre Belloni
2013-09-21 21:37 ` Otavio Salvador
2013-09-22 10:48 ` Alexandre Belloni [this message]
2013-09-22 20:27 ` Otavio Salvador
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=523ECB17.5010103@free-electrons.com \
--to=alexandre.belloni@free-electrons.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.