From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: Warnings from autotools_copy_aclocals()
Date: Thu, 14 Apr 2016 09:14:51 +0100 [thread overview]
Message-ID: <1460621691.9308.162.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=VDX8QpecxVbjEJNyxiymp9CeqcqYXV2-ARTML4ZdiAjw@mail.gmail.com>
On Wed, 2016-04-13 at 16:58 -0700, Andre McCurdy wrote:
> Does anyone else see these type of warnings from
> autotools_copy_aclocals()? I don't remember exactly when they started
> (a few months ago at least, maybe more).
>
> WARNING: gmp-4.2.1-r0 do_configure:
> /.../build-dcx960-debug/tmp/sstate-control/manifest-dcx960-debug
> -glibc-initial.populate_sysroot
> not found
> WARNING: gmp-4.2.1-r0 do_configure:
> /.../build-dcx960-debug/tmp/sstate-control/manifest-dcx960-debug
> -libgcc-initial.populate_sysroot
> not found
Yes, I also do have a rough idea of the cause.
They happen in builds from sstate where the system has decided that for
whatever reason, a given dependency isn't needed. The aclocal
dependency traversal code looks down the full dependency list and warns
when these things aren't present.
Examples of sstate's decisions would be skipping libgcc-initial when
libgcc is available, same for glibc-initial and glibc.
Somehow we need to reconcile the two views. sstate is clearly correct
or there would be failures. The question is how to make the aclocal
code have the same understanding (which will then limit the number of
aclocal macros copied in).
Cheers,
Richard
prev parent reply other threads:[~2016-04-14 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 23:58 Warnings from autotools_copy_aclocals() Andre McCurdy
2016-04-14 8:14 ` Richard Purdie [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=1460621691.9308.162.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox