GNU bug report logs - #28308
Build failure on FreeBSD/aarch64

Previous Next

Full log

View this message in rfc822 format

From: Gergely Czuczy <gergely.czuczy <at> harmless.hu>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 28308 <at> debbugs.gnu.org, npostavs <at> users.sourceforge.net
Subject: bug#28308: Build failure on FreeBSD/aarch64
Date: Mon, 11 Sep 2017 21:57:47 +0200

On 2017. 09. 11. 19:17, Eli Zaretskii wrote:
>> Cc: npostavs <at> users.sourceforge.net, 28308 <at> debbugs.gnu.org
>> From: Gergely Czuczy <gergely.czuczy <at> harmless.hu>
>> Date: Mon, 11 Sep 2017 19:12:12 +0200
>>
>>> That's a call to delete_terminal, which doesn't appear in your
>>> backtrace, and doesn't call xpalloc, either.  So thanks, but I'm still
>>> confused.  Are you sure this is an unoptimized build?  Is it possible
>>> that we are looking at LLDB bug?
>> It's the lldb debug, right. And I'm sure it's an unoptimized build, I've
>> went back and checked the build flags:
>> cc -Demacs  -I. -I. -I../lib -I../lib
>> -I/usr/local/include/libxml2             -MMD -MF deps/.d -MP
>> -Wno-switch -Wno-pointer-sign -Wno-string-plus-int
>> -Wno-unknown-attributes -Wno-initializer-overrides
>> -Wno-tautological-compare
>> -Wno-tautological-constant-out-of-range-compare -O0 -g
>> -fno-strict-aliasing  -Wl,-znocombreloc  (...)
>>
>> If that helps, I can create a qemu VM with this fbsd build, and give you
>> the image.
> Would it be possible for you to install GDB, and then repeat the same
> experiment under GDB?
Unfortunately that won't work:
# make install
===>  gdb-8.0_1 is only for amd64 armv6 i386 mips powerpc powerpc64, while
you are running aarch64.

However, I've found that clang is able to tune the debug info for lldb 
with -glldb. Let me try that. It might take a bit of time, and it's 10pm 
here, so might get back with that tomorrow.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.