From: Bryan Hundven <bryanhundven@gmail.com>
To: Daniel Price <daniel.price@gmail.com>
Cc: <crossgcc@sourceware.org>
Subject: Re: Problems with recent expat/gdb changes
Date: Wed, 05 Jun 2013 08:19:00 -0000 [thread overview]
Message-ID: <CDD42BDE.1C1DC%bryanhundven@gmail.com> (raw)
In-Reply-To: <CAKduhSspMV0vMEQ3=vGPqfH0iv=uZudmN=HQ3ScynZb+m_LuPA@mail.gmail.com>
Daniel,
On 6/4/13 10:28 PM, "Daniel Price" <daniel.price@gmail.com> wrote:
>Hi all,
>
>I've had some trouble with the recent trunk commits that change the
>way expat is handled. A bare-metal mips toolchain I used to be able
>to build using crosstool-ng 0.17 now won't compile after moving to
>trunk crosstool-ng:
>
>[INFO ] =================================================================
>[INFO ] Installing cross-gdb
>[EXTRA] Configuring cross-gdb
>[EXTRA] Building cross-gdb
>[ERROR] configure: error: expat is missing or unusable
>[ERROR] make[2]: *** [configure-gdb] Error 1
>[ERROR] make[1]: *** [all] Error 2
>[ERROR]
>[ERROR] >>
>[ERROR] >> Build failed in step 'Installing cross-gdb'
>[ERROR] >> called in step '(top-level)'
>[ERROR] >>
>[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@257]
>[ERROR] >> called from:
>do_debug_gdb_build[scripts/build/debug/300-gdb.sh@170]
>[ERROR] >> called from: do_debug[scripts/build/debug.sh@35]
>[ERROR] >> called from: main[scripts/crosstool-NG.sh@632]
>[ERROR] >>
>[ERROR] >> For more info on this error, look at the file: 'build.log'
>[ERROR] >> There is a list of known issues, some with workarounds, in:
>[ERROR] >>
>'/tmp/x86_64-fc15-tools/crosstool-ng/share/doc/crosstool-ng/ct-ng.hg+unkno
>wn-20130604.175703/B
>- Known issues.txt'
>[ERROR]
>
>I have placed the config here:
>https://gist.github.com/danielbprice/5711220
>
>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
s/crosstool-ng/gdb/
> is expecting libexpat to be on the host
>system... but I think in this case (as in some other cases handled by
>the gdb script), expat should probably be downloaded and linked in by
>crosstool-ng, to avoid a dependency on the host system. Thanks for
>any input you can provide.
There is definitely some funkyness with expat being needed to be built
here.
I feel that libexpat should be broken out of 300-gdb.sh and into it's own
script and depended on by specific component versions (say gdb >= 7.3) in
Kconfig, so the user can also say if they want expat (which is needed by
python support) or if the version requires it.
I don't think you'll want expat on static cross_gdb, so a short term
solution could be to comment out lines 126 and 127 from
scripts/build/debug/300-gdb.sh. Then rebuild and reinstall ct-ng.
>
> -dp
>
>--
>Daniel.Price@gmail.com; Twitter: @danielbprice
>
>--
>For unsubscribe information see http://sourceware.org/lists.html#faq
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2013-06-05 8:19 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 [this message]
2013-06-05 10:44 ` Trevor Woerner
2013-06-05 14:22 ` Bryan Hundven
2013-06-05 19:01 ` Daniel Price
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=CDD42BDE.1C1DC%bryanhundven@gmail.com \
--to=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=daniel.price@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).