From: Daniel Price <daniel.price@gmail.com>
To: Bryan Hundven <bryanhundven@gmail.com>
Cc: Trevor Woerner <twoerner@gmail.com>,
"crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Problems with recent expat/gdb changes
Date: Wed, 05 Jun 2013 19:01:00 -0000 [thread overview]
Message-ID: <CAKduhSvovF=ARatXGYeEPZsNBYugnattp-MAVOv2NimCgGOz+g@mail.gmail.com> (raw)
In-Reply-To: <CDD49468.1C2C9%bryanhundven@gmail.com>
Thanks for the followups. Rather than modify the code, my short-term
workaround was to add "--disable-expat --with-expat=no" to the "extra
gdb configure args" since the target in this particular case does not
need XML support.
Personally I think the answer is that, when building a static
cross-gdb, expat should just always be built.
-dp
On Wed, Jun 5, 2013 at 7:22 AM, Bryan Hundven <bryanhundven@gmail.com> wrote:
> Trevor,
>
> On 6/5/13 3:44 AM, "Trevor Woerner" <twoerner@gmail.com> wrote:
>
>>On Wed, Jun 5, 2013 at 4:18 AM, Bryan Hundven <bryanhundven@gmail.com>
>>wrote:
>>> On 6/4/13 10:28 PM, "Daniel Price" <daniel.price@gmail.com> wrote:
>>>>This is on a system where libexpat-dev / -devel isn't installed.
>>>>
>>>>It seems to me that there's an issue where, despite requesting static
>>>>cross-gdb, crosstool-ng
>>>> is expecting libexpat to be on the host
>>>>system
>>>
>>> There is definitely some funkyness with expat being needed to be built
>>> here.
>>
>>
>>Some target boards, such as the boards from ST, send their details
>>(memory areas, register info, etc) to the host via XML (i.e. when
>>using st-link). Therefore there are times when a cross-gdb needs expat
>>to process this incoming information:
>>
>>http://sourceware.org/ml/crossgcc/2013-03/msg00005.html
>>
>>I'm not trying to say this shouldn't be configurable or that expat
>>handling shouldn't be broken out into its own script; I'm just
>>pointing out that there are valid times when someone would want expat
>>included in gdb-cross.
>>
>>Best regards,
>> Trevor
>
> The "funkiness" (now with spell check) that I was talking about is that
> expat was only built for native gdb.
> My suggestion is _that_ is what is odd. So now I'm just being clear that
> we are in agreement ;)
>
> The other part of the "funkiness" was while I was reading through
> 300-gdb.sh, I can see parts of it that need updating.
> So fixing 300-gdb.sh to build expat and gdb for cross_gdb might be a
> little more work.
>
> -Bryan
>
>
--
Daniel.Price@gmail.com; Twitter: @danielbprice
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2013-06-05 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 5:28 Daniel Price
2013-06-05 8:19 ` Bryan Hundven
2013-06-05 10:44 ` Trevor Woerner
2013-06-05 14:22 ` Bryan Hundven
2013-06-05 19:01 ` Daniel Price [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='CAKduhSvovF=ARatXGYeEPZsNBYugnattp-MAVOv2NimCgGOz+g@mail.gmail.com' \
--to=daniel.price@gmail.com \
--cc=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=twoerner@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).