From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Broken parallel build of gcc*
Date: Fri, 20 Jul 2012 13:28:03 +0100 [thread overview]
Message-ID: <1342787283.21788.13.camel@ted> (raw)
In-Reply-To: <ly1uk67hna.fsf@ensc-virt.intern.sigma-chemnitz.de>
On Fri, 2012-07-20 at 14:15 +0200, Enrico Scholz wrote:
> Richard Purdie
> <richard.purdie-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
> writes:
>
> >> Is there a way to exclude such tasks from the signature handling?
> >
> > The easiest option is probably something like:
> >
> > do_rm_old_works[vardepexclude] = "PN"
>
> I tried this but it is not really an option because there must be added
> a lot of completely unrelated variables:
>
> $ bitbake-diffsigs gcc-runtime*do_rm_old_work.sigdata* libgcc*do_rm_old_work.sigdata*
>
> Dependency on variable gcc_cv_collect2_libs was added
> Variable CPPFLAGS value changed from to ${TARGET_CPPFLAGS}
>
> (none of these is used within do_rm_old_works).
Can you point me at a copy of the class your using and the full diffsigs
output please?
Thanks,
Richard
next prev parent reply other threads:[~2012-07-20 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 10:28 Broken parallel build of gcc* Enrico Scholz
2012-07-20 10:41 ` Martin Jansa
2012-07-20 11:06 ` Richard Purdie
2012-07-20 11:53 ` Enrico Scholz
2012-07-20 12:04 ` Richard Purdie
2012-07-20 12:15 ` Enrico Scholz
2012-07-20 12:28 ` Richard Purdie [this message]
2012-07-20 12:30 ` Martin Jansa
2012-07-20 12:44 ` Enrico Scholz
2012-07-21 14:39 ` Enrico Scholz
2012-07-22 8:43 ` Richard Purdie
2012-07-22 9:43 ` Enrico Scholz
2012-07-22 10:35 ` Richard Purdie
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=1342787283.21788.13.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 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.