From: Chris Conroy <Chris.Conroy@hillcrestlabs.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: meta-toolchain continues to woe
Date: Thu, 12 Nov 2009 10:14:29 -0500 [thread overview]
Message-ID: <1258038869.4924.67.camel@conroy-linux> (raw)
In-Reply-To: <6ec4247d0911112034v54f570ccn4c4334a1da094f0d@mail.gmail.com>
On Thu, 2009-11-12 at 15:04 +1030, Graham Gower wrote:
> 2009/11/12 Holger Hans Peter Freyther <holger+oe@freyther.de>:
> >
> > ./run.do_populate_sdk.27727
> > Collected errors:
> > * Could not obtain administrative lock for offline root (ERR: Bad file
> > descriptor) at /data/openembedded/build/arm/cortex-a8/tmp/work/x86_64-armv7a-
> > sdk-angstrom-linux-gnueabi/meta-toolchain-1.0-r0/sdk/image//usr/lib/opkg/lock
>
> Presumably, the lock file could not be creat()ed. Unfortunately, there
> is no error checking on that creat() call in opkg and you don't get a
> useful error message.
I submitted a patch to opkg back in September to fix this error message
to be a bit more useful. If you upgrade to opkg >=216 it will save you
some headaches whenever this error occurs.
http://code.google.com/p/opkg/issues/detail?id=22
--Chris Conroy
next prev parent reply other threads:[~2009-11-12 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 3:57 meta-toolchain continues to woe Holger Hans Peter Freyther
2009-11-12 4:34 ` Graham Gower
2009-11-12 4:49 ` Holger Hans Peter Freyther
2009-11-12 5:11 ` Holger Hans Peter Freyther
2009-11-12 12:09 ` Richard Purdie
2009-11-12 12:28 ` Holger Hans Peter Freyther
2009-11-12 15:14 ` Chris Conroy [this message]
2009-11-12 15:29 ` Chris Conroy
2009-11-12 21:16 ` Graham Gower
2009-11-13 19:48 ` Khem Raj
2009-11-13 1:19 ` Holger Hans Peter Freyther
2009-11-13 15:58 ` Chris Conroy
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=1258038869.4924.67.camel@conroy-linux \
--to=chris.conroy@hillcrestlabs.com \
--cc=openembedded-devel@lists.openembedded.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.