From: Jonathan Cameron <jic23@cam.ac.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: missing dependency on expat-native in gdb-cross-sdk-7.1-r7.0
Date: Wed, 29 Sep 2010 16:55:18 +0100 [thread overview]
Message-ID: <4CA36166.1000003@cam.ac.uk> (raw)
In-Reply-To: <4CA35464.5030007@freyther.de>
On 09/29/10 15:59, Holger Freyther wrote:
> On 09/29/2010 10:32 PM, Jonathan Cameron wrote:
>> Hi all,
>
>>
>> I'd suggest adding expat-native to gdb-cross-sdk.inc DEPENDS (which seems to fix the problem) No idea if it is needed
>> for all versions though.
>
> At least GDB 7.x needs expat to parse the register definitions for the CPU.
> E.g. this is important when using the gdb remote protocol.
>
> You should also pass --with-expat to it, right now I have a build issue with
> the target gdb and this argument.
>
Ah, thanks for the heads up. I'll try that and see how I get on.
As an aside there is also an issue with both binutils-cross-sdk and gdb-cross-sdk
wanting to install libiberty.a
next prev parent reply other threads:[~2010-09-29 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 14:32 missing dependency on expat-native in gdb-cross-sdk-7.1-r7.0 Jonathan Cameron
2010-09-29 14:59 ` Holger Freyther
2010-09-29 15:55 ` Jonathan Cameron [this message]
2010-09-29 22:30 ` Graham Gower
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=4CA36166.1000003@cam.ac.uk \
--to=jic23@cam.ac.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox