From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: poky@yoctoproject.org
Subject: dora regression: "WARNING: Duplicate inclusion for meta/recipes-core/eglibc/eglibc-common.inc in meta/recipes-core/eglibc/eglibc-initial.inc"
Date: Sun, 05 Jan 2014 13:10:37 +0100 [thread overview]
Message-ID: <52C94BBD.6030307@message-id.googlemail.com> (raw)
This commit
commit 564c687c2a2b90f277f444eed298b6defc51c467
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Fri Nov 29 23:15:56 2013 +0000
bitbake: parse/ConfHander/BBHandler/utils: Fix cache dependency bugs
Leads to lots of
WARNING: Duplicate inclusion for
/space/tmp/yocto-test/meta/recipes-core/eglibc/eglibc-common.inc in
/space/tmp/yocto-test/meta/recipes-core/eglibc/eglibc-initial.inc
I think the problem is not with this commit but with eglibc recipes:
eglibc-initial_2.18.bb:1: including eglibc_2.18.bb
eglibc_2.18.bb:1: including eglibc.inc
eglibc.inc:1: including eglibc-common.inc
....
eglibc-initial_2.18.bb:2: including eglibc-initial.inc
eglibc-initial.inc:1: including eglibc-common.inc
So eglibc-common.inc is really included twice.
I'm in no case expert enough to tell which of the includes could or
should be omitted, but I'd probably remove the one in eglibc-initial.inc
Best regards,
Stefan
--
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
next reply other threads:[~2014-01-05 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 12:10 Stefan Seyfried [this message]
2014-01-05 13:11 ` dora regression: "WARNING: Duplicate inclusion for meta/recipes-core/eglibc/eglibc-common.inc in meta/recipes-core/eglibc/eglibc-initial.inc" Martin Jansa
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=52C94BBD.6030307@message-id.googlemail.com \
--to=stefan.seyfried@googlemail.com \
--cc=poky@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.