From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Trevor Woerner <twoerner@gmail.com>
Subject: Re: build failure in native gdb with crosstool-ng-1.13.1 on openSUSE 12.1
Date: Tue, 29 Nov 2011 22:54:00 -0000 [thread overview]
Message-ID: <201111292353.31922.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <CAHUNapQufm7T=Bich5YFXmzntqdp7LEm_tPw-RMPDao_PW4ktQ@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 2032 bytes --]
Trevor, All,
On Tuesday 29 November 2011 00:19:13 Trevor Woerner wrote:
> 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".
What target are youbuilding for? Could you post your .config, please?
> Manually
> tweaking the above to say "lib64" allows the native gdb build to
> succeed (but, obviously, is not a general solution).
I never encountered this issue, but it can make sense if the target
architecture is 64-bit, in which case the libraries could be installed
in the lib64 sub-directory
Care to test the attached patch, please?
> The build then fails a little later (during cleanup, stripping all
> binaries) but I haven't looking into that yet to provide much
> information.
Probably again an issue with lib vs. lib64 confusion along the road...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
[-- Attachment #2: debug-gdb-native-fix-64bit-targets.patch --]
[-- Type: text/x-patch, Size: 821 bytes --]
diff --git a/scripts/build/debug/300-gdb.sh b/scripts/build/debug/300-gdb.sh
--- a/scripts/build/debug/300-gdb.sh
+++ b/scripts/build/debug/300-gdb.sh
@@ -191,6 +191,13 @@
native_extra_config=("${extra_config[@]}")
+ # For 64-bit targets, the target libs may get installed in lib64/
+ # and not in lib/ so symlink the former to the latter.
+ CT_DoExecLog DEBUG mkdir -p "${CT_BUILD_DIR}/static-target"
+ CT_DoExecLog DEBUG mkdir -p "${CT_BUILD_DIR}/static-target/lib"
+ CT_DoExecLog DEBUG ln -s "${CT_BUILD_DIR}/static-target/lib" \
+ "${CT_BUILD_DIR}/static-target/lib64"
+
# GDB on Mingw depends on PDcurses, not ncurses
if [ "${do_ncurses}" = "y" ]; then
CT_DoLog EXTRA "Building static target ncurses"
[-- Attachment #3: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-11-29 22:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 23:19 Trevor Woerner
2011-11-29 22:54 ` Yann E. MORIN [this message]
[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=201111292353.31922.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=twoerner@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).