From: Jaap de Jong <jaap.dejong@nedap.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: error when bitbaking console-base-image (danny)
Date: Thu, 11 Apr 2013 15:04:59 +0200 [thread overview]
Message-ID: <5166B4FB.7080100@nedap.com> (raw)
In-Reply-To: <20130411123313.GD2477@jama>
On 04/11/2013 02:33 PM, Martin Jansa wrote:
> On Thu, Apr 11, 2013 at 02:01:42PM +0200, Jaap de Jong wrote:
>> Hi All,
>> I've been experimenting with images, and every time I get this error
>> even with a completely fresh build directory:
>>
>> log_check: There were error messages in the logfile
>> log_check: Matched keyword: [Collected errors]
>>
>> Configuring connman.
>> Configuring connman-systemd.
>> Configuring tinylogin.
>> Configuring angstrom-version.
>> Configuring angstrom-packagegroup-boot.
>> Collected errors:
>> * extract_archive: Cannot create symlink from ./var/log to
>> 'volatile/log': File exists.
>> * extract_archive: Cannot create symlink from ./var/run to
>> 'volatile/run': File exists.
> Looks like you have inconsistency between fs-perms.txt
> (e.g. default openembedded-core/meta/files/fs-perms.txt)
> and what .ipk files are packaging as /var/log and /var/run (probably
> from base-files, but /var/run is also included in dbus and other
> packages).
No differences with denzil.
I did a bitbake core-image-base and that compiles without a problem.
Thanks for sharing our thoughts!
>> + '[' '!' -z '' ']'
>> + package_tryout_install_multilib_ipk
>> + multilib_tryout_dirs=
>>
>>
>> Could really use some help here...
>> Thanks!
>> Jaap
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2013-04-11 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 12:01 error when bitbaking console-base-image (danny) Jaap de Jong
2013-04-11 12:33 ` Martin Jansa
2013-04-11 13:04 ` Jaap de Jong [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=5166B4FB.7080100@nedap.com \
--to=jaap.dejong@nedap.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.