[Buildroot] Analysis of autobuild failures 18-19/11

[Arnout Vandecappelle]

On 21-11-16 12:21, Waldemar Brodkorb wrote:
> Hi,
> Arnout Vandecappelle wrote,
> 
>>  Hi all,
>>
>>  Here's an analysis of autobuild failures. It looks a bit different from what
>> Thomas usually sends because I based it on the website rather than the mail. I
>> eliminated the ones that are already fixed in git, and also the powerpc64le
>> failures that are due to libtool.m4.
>>
>>  I'm not putting the people from get-developers in Cc, because they already get
>> these mails.
>>
>> http://autobuild.buildroot.net/results/d47fa41aa860d82471b83ac90967d3a3dacd8611
>> m68k / 5208	lcdapi-v0.10	uclibc	static
>>
>>> /tmp/cc6S5lwR.s: Assembler messages:
>>> /tmp/cc6S5lwR.s: Internal error, aborting at dw2gencfi.c:214 in emit_expr_encoded
>>> Please report this bug.
>>> Makefile:784: recipe for target 'lcdapi/api/liblcdapi_la-LCDHorizontalBar.lo' failed
>>
>>  ICE... Waldemar?
> 
> This could be avoided by using something like the following (example
> for libasplib):
> diff --git a/package/libasplib/libasplib.mk
> b/package/libasplib/libasplib.mk
> index 41aeaeb..b09d739 100644
> --- a/package/libasplib/libasplib.mk
> +++ b/package/libasplib/libasplib.mk
> @@ -10,4 +10,11 @@ LIBASPLIB_LICENSE = GPLv3+
>  LIBASPLIB_LICENSE_FILES = LICENSE
>  LIBASPLIB_INSTALL_STAGING = YES
>  
> +# Internal error, aborting at dw2gencfi.c:214 in emit_expr_encoded
> +ifeq ($(BR2_m68k_cf),y)
> +LIBASPLIB_CXXFLAGS += -fno-dwarf2-cfi-asm
> +endif
> +
> +LIBASPLIB_CONF_OPTS += -DCMAKE_CXX_FLAGS="$(TARGET_CXXFLAGS) $(LIBASPLIB_CXXFLAGS)"
> +
>  $(eval $(cmake-package))
> 
> Unfortunately libasplib cmake infrastructure ignores my
> CMAKE_CXX_FLAGS. 
> 
> The m68k/coldfire uclinux seems to have some limitation regarding
> CFI assembly generation, as elf2flt lacks some features.
> See here for the comment in the code of GNU as:
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gas/config/tc-m68k.h;h=30ca2cb35e0b00048c52bda0dc04ae0cdef5cc3a;hb=HEAD#l180
> 
> With gcc -fno-dwarf2-cfi-asm we can disable the CFI generation and
> at least fix the compile errors for those packages.
>  
> Not sure if it will break some exception handling in C++ code or if
> it only disables the ability to debug the code.

 If it doesn't break things (and you can do runtime test, right?), maybe we
should just pass -fno-dwarf2-cfi-asm in the wrapper for coldfire?

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF