From: Trevor Woerner <twoerner@gmail.com>
To: crossgcc@sourceware.org
Subject: build failure in native gdb with crosstool-ng-1.13.1 on openSUSE 12.1
Date: Mon, 28 Nov 2011 23:19:00 -0000 [thread overview]
Message-ID: <CAHUNapQufm7T=Bich5YFXmzntqdp7LEm_tPw-RMPDao_PW4ktQ@mail.gmail.com> (raw)
Hi Yann,
I recently upgraded to the latest openSUSE 12.1 release and discovered
that crosstool-NG has trouble building native gdb.
In scripts/build/debug/300-gdb.sh around line 249 is found:
native_extra_config+=("--with-curses")
# There's no better way to tell gdb where to find -lcurses... :-(
gdb_native_CFLAGS+=("-I${CT_BUILD_DIR}/static-target/include")
gdb_native_CFLAGS+=("-L${CT_BUILD_DIR}/static-target/lib")
In previous builds (i.e. openSUSE 11.4, etc) the lib directory (as
specified) exists. With my builds on openSUSE 12.1 this directory
doesn't exist, but ${CT_BUILD_DIR}/static-target/lib64 does. The
native gdb fails during the run of one of the many sub-directory
./configure scripts saying "no termcap library found". Manually
tweaking the above to say "lib64" allows the native gdb build to
succeed (but, obviously, is not a general solution).
The build then fails a little later (during cleanup, stripping all
binaries) but I haven't looking into that yet to provide much
information.
Best regards,
Trevor
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2011-11-28 23:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 23:19 Trevor Woerner [this message]
2011-11-29 22:54 ` Yann E. MORIN
[not found] ` <CAHUNapRiJtqH3yJDztc-ZroJKzjgRWuSwDKNjZVYYSn5iM0ryA@mail.gmail.com>
2011-11-30 2:46 ` Trevor Woerner
2011-12-05 22:36 ` Trevor Woerner
2011-12-11 21:44 ` Yann E. MORIN
2011-12-12 12:36 ` Yann E. MORIN
2011-12-12 13:54 ` Trevor Woerner
2011-12-12 14:07 ` Yann E. MORIN
2011-12-12 21:53 ` Trevor Woerner
2011-12-12 22:43 ` Yann E. MORIN
2011-12-13 3:43 ` Trevor Woerner
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='CAHUNapQufm7T=Bich5YFXmzntqdp7LEm_tPw-RMPDao_PW4ktQ@mail.gmail.com' \
--to=twoerner@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).