Problems with recent expat/gdb changes

Problems with recent expat/gdb changes

[Daniel Price]

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

        -dp

--
Daniel.Price@gmail.com; Twitter: @danielbprice

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Problems with recent expat/gdb changes

[Bryan Hundven]

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

Re: Problems with recent expat/gdb changes

[Trevor Woerner]

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

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Problems with recent expat/gdb changes

[Bryan Hundven]

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



--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Problems with recent expat/gdb changes

[Daniel Price]

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