From: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
To: 'Stefan Hallas Mulvad' <shm@hallas.nu>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: RE: GDB build failure from tip
Date: Tue, 26 Jul 2016 23:04:00 -0000 [thread overview]
Message-ID: <F9C551623D2CBB4C9488801D14F864C6EE86C087@ex-mb1.corp.adtran.com> (raw)
In-Reply-To: <016D099B-EDBA-4F00-89B4-0BC50E95A99E@hallas.nu>
> It be great if you could post your build.log, or at least some more information from it.
>
> A while back I faced a, what seams to be, similar issue. I proposed a patch which was rejected,
> however we use it at work and I know it has worked for several other people so give it a try.
Looks like others that I have seen on various groups.
I don't think this will help in my situation.
The problem is that when I "file" the gdb for the cross,
it is x86_64. The native doesn't build.
I thought the information I provided was enough... Sorry about that!
For what it is worth, in the 300-gdb.sh, the test above was
_NATIVE_..., then the CC was set to TARGET, and vice versa:
Line 95:
CC_for_gdb="${CT_HOST}-gcc ${CT_CFLAGS_FOR_HOST} ${CT_LDFLAGS_FOR_HOST}"
LD_for_gdb="${CT_HOST}-ld ${CT_LDFLAGS_FOR_HOST}"
if [ "${CT_GDB_CROSS_STATIC}" = "y" ]; then
CC_for_gdb+=" -static"
LD_for_gdb+=" -static"
fi
Line 195:
[ "${CT_TOOLCHAIN_ENABLE_NLS}" != "y" ] && \
native_extra_config+=("--disable-nls")
if [ "${CT_GDB_NATIVE_STATIC}" = "y" ]; then
CC_for_gdb="${CT_TARGET}-gcc -static"
LD_for_gdb="${CT_TARGET}-ld -static"
else
CC_for_gdb="${CT_TARGET}-gcc"
LD_for_gdb="${CT_TARGET}-ld"
fi
Thanks for the info, though!
Andy
>
> Hope it works,
>
> Best regards,
> Stefan
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2016-07-26 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 22:46 ANDY KENNEDY
2016-07-26 22:57 ` Stefan Hallas Mulvad
2016-07-26 23:04 ` ANDY KENNEDY [this message]
2016-07-27 0:13 ` ANDY KENNEDY
2016-07-27 17:32 ` ANDY KENNEDY
2016-07-27 18:11 ` Stefan Hallas Mulvad
2016-07-27 20:19 ` ANDY KENNEDY
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=F9C551623D2CBB4C9488801D14F864C6EE86C087@ex-mb1.corp.adtran.com \
--to=andy.kennedy@adtran.com \
--cc=crossgcc@sourceware.org \
--cc=shm@hallas.nu \
/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).