GDB build failure from tip
ANDY KENNEDY
ANDY.KENNEDY@adtran.com
Tue Jul 26 23:04:00 GMT 2016
> 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
More information about the crossgcc
mailing list