From: Jack Mitchell <ml@communistcode.co.uk>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Qemu refusing to build
Date: Thu, 02 Aug 2012 17:28:58 +0100 [thread overview]
Message-ID: <501AAACA.2010903@communistcode.co.uk> (raw)
In-Reply-To: <1343922080.9756.79.camel@ted>
On 02/08/2012 16:41, Richard Purdie wrote:
> On Thu, 2012-08-02 at 16:28 +0100, Jack Mitchell wrote:
>> How would I manually attempt to configure? There are no files what so
>> ever in the
>> /mnt/storage/yoctoBuilds/poky-vanilla.git/build/tmp/work/x86_64-linux/qemu-native-0.15.1-r10/qemu-0.15.1
>> directory.
>
> Well, that is a big help to know. It sounds like something has wiped the
> work directory and its then trying to rebuild it. Are you using rm_work
> of some kind? It sounds like some kind of malfunction has occurred with
> it...
>
> Cheers,
>
> Richard.
>
It could very well be related to the fact that I am building over NFS
and the other problems that have come with it. I'm building with the bog
standard vanilla poky with quemu arm uncommented. In this situation I
would normally -c cleansstate and try again, but that function is also
broken for me (again possibly NFS related).
I changed my NFS mount settings to force sync which makes it act like a
more traditional hard drive but it doesn't seem to have done me any good.
I'm not back in work till Monday so I'll see if I can do anything more
with it then. If anyone could confirm that they build on an NFS mount
then that would be a massive help.
Cheers,
prev parent reply other threads:[~2012-08-02 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 9:10 Qemu refusing to build Jack Mitchell
2012-08-02 13:40 ` Richard Purdie
2012-08-02 15:28 ` Jack Mitchell
2012-08-02 15:41 ` Richard Purdie
2012-08-02 16:28 ` Jack Mitchell [this message]
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=501AAACA.2010903@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.