From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
"Burton, Ross" <ross.burton@intel.com>,
openembedded-core@lists.openembedded.org
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Rudolf J Streif <rudolf.streif@gmail.com>
Subject: Re: Wrong sstate signatures for cross toolchain Was: [yocto] Building gdb-7.10 for arm with master
Date: Wed, 09 Mar 2016 22:51:33 +0000 [thread overview]
Message-ID: <1457563893.2804.195.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160309225058.GM2542@jama>
On Wed, 2016-03-09 at 23:50 +0100, Martin Jansa wrote:
> On Sat, Mar 05, 2016 at 09:40:48PM +0000, Burton, Ross wrote:
> > On 5 March 2016 at 21:19, Rudolf J Streif <rudolf.streif@gmail.com>
> > wrote:
> >
> > > compile fails with the following error message:
> > >
> > > > make[2]: *** No rule to make target
> > > > '../readline/libreadline.a', needed
> > > by 'gdb'. Stop.
> > > > make[2]: *** Waiting for unfinished jobs....
> > >
> > > The reason seems to be a broken path to the built-in readline in
> > > the
> > > makefile as the default configuration is
> > > --without-system-readline. Enabling
> > >
> > > PACKAGECONFIG_append_pn-dbg = " readline"
>
> See http://patchwork.openembedded.org/patch/116843/ discussion, the
> patch from Ross mentioned bellow fixes it better and is already
> merged
> in master.
>
> > The default is with system readline...
> >
> > gdb-common.inc:PACKAGECONFIG ??= "readline"
>
> BTW: this is causing gdb-cross-* to depend on target readline, which
> may
> have different signatures for different MACHINEs with the same arch.
>
> E.g. after adding qemuarm7 MACHINE, you can easily get gdb-cross-arm
> being rebuilt/extracted-from-sstate after each MACHINE change.
>
> I'm not sure why selftest didn't catch this, but it can be seen with:
> openembedded-core/scripts/sstate-diff-machines.sh --machines="qemuarm
> qemuarm7" --targets=gdb-cross-arm --tmpdir=tmp-glibc
Something has regressed. Do you know when this last passed? Looks like
we need to add some extra tests to selftest and get this fixed.
Sadly I'm drowning in problems to fix at the moment :(
Cheers,
Richard
next prev parent reply other threads:[~2016-03-09 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18448427.V3ACvxT67R@rjs-zotac.streifs.net>
[not found] ` <CAJTo0La2CZAKw0Cd4_NpPLt=qXy3x3Arv36huhUMmCH3tV14YA@mail.gmail.com>
2016-03-09 22:50 ` Wrong sstate signatures for cross toolchain Was: [yocto] Building gdb-7.10 for arm with master Martin Jansa
2016-03-09 22:51 ` Richard Purdie [this message]
2016-03-09 23:02 ` Richard Purdie
2016-03-09 23:52 ` Martin Jansa
2016-03-10 0:09 ` Richard Purdie
2016-03-10 10:34 ` Peter A. Bigot
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=1457563893.2804.195.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=rudolf.streif@gmail.com \
--cc=yocto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox