Problems with recent expat/gdb changes

Daniel Price
Wed Jun 5 05:28:00 GMT 2013

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]  >>  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:
[ERROR]  >>        called from: do_debug[scripts/build/]
[ERROR]  >>        called from: main[scripts/]
[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]  >>
- Known issues.txt'

I have placed the config here:

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... 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.


--; Twitter: @danielbprice

For unsubscribe information see

More information about the crossgcc mailing list