public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Chris Wilkinson" <winstonian36@gmail.com>
To: "'crossgcc'" <crossgcc@sourceware.org>
Subject: RE: ct-ng v1.13.3 - build fails at GDB
Date: Tue, 24 Jan 2012 18:24:00 -0000	[thread overview]
Message-ID: <003501ccdac5$6b1ee0e0$415ca2a0$@com> (raw)
In-Reply-To: <CAHUKsLJxyAC+ZLE=UdNQZM4tfeD29pxCb+rFB+QsSWX9TwyjpQ@mail.gmail.com>

I should have mentioned that expat/libexpat1 are installed (Ubuntu 11.1).

-----Original Message-----
From: crossgcc-owner@sourceware.org [mailto:crossgcc-owner@sourceware.org]
On Behalf Of Chris Wilkinson
Sent: Tuesday, January 24, 2012 12:04 PM
To: crossgcc
Subject: ct-ng v1.13.3 - build fails at GDB

The build fails thus using mipsel-unknown-linux-gnu config from samples
folder.

.....
[ALL  ]    checking for library containing tgetent... none required
[ALL  ]    checking whether to use expat... yes
[ALL  ]    checking for ld used by GCC... i686-build_pc-linux-gnu-ld
[ALL  ]    checking if the linker (i686-build_pc-linux-gnu-ld) is GNU ld...
yes
[ALL  ]    checking for shared library run path origin... done
[ALL  ]    checking for libexpat... no
[ERROR]    configure: error: expat is missing or unusable
[ERROR]    make[2]: *** [configure-gdb] Error 1
[ALL  ]    make[2]: Leaving directory
`/home/chrisw/crosstool-ng-1.13.3/.build/mipsel-unknown-linux-gnu/build/buil
d-gdb-cross'
[ERROR]    make[1]: *** [all] Error 2
[ALL  ]    make[1]: Leaving directory
`/home/chrisw/crosstool-ng-1.13.3/.build/mipsel-unknown-linux-gnu/build/buil
d-gdb-cross'
[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@172]
[ERROR]  >>        called from:
do_debug_gdb_build[scripts/build/debug/300-gdb.sh@153]
[ERROR]  >>        called from: do_debug[scripts/build/debug.sh@35]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@595]
[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]  >>      'docs/B - Known issues.txt'
[ERROR]
[ERROR]  (elapsed: 97:44.80)

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


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

  reply	other threads:[~2012-01-24 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 17:04 Chris Wilkinson
2012-01-24 18:24 ` Chris Wilkinson [this message]
2012-01-25 21:59   ` Chris Wilkinson

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='003501ccdac5$6b1ee0e0$415ca2a0$@com' \
    --to=winstonian36@gmail.com \
    --cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).