From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of autobuild failures 18-19/11
Date: Wed, 23 Nov 2016 12:37:02 +0100 [thread overview]
Message-ID: <20161123113702.GZ27313@waldemar-brodkorb.de> (raw)
In-Reply-To: <44bda1d2-3859-54a7-0ffc-f4b193bfc3e8@mind.be>
Hi Arnout,
Arnout Vandecappelle wrote,
> 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?
I don't know the internals of the wrapper, could you suggest a
patch, then I can do some testing with either Qemu or some real
board.
best regards
Waldemar
next prev parent reply other threads:[~2016-11-23 11:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 19:23 [Buildroot] Analysis of autobuild failures 18-19/11 Arnout Vandecappelle
2016-11-19 20:55 ` Romain Naour
2016-11-20 15:24 ` Arnout Vandecappelle
2016-11-20 23:18 ` Sam Bobroff
2016-11-24 20:48 ` Arnout Vandecappelle
2016-11-25 0:51 ` Sam Bobroff
2016-11-21 11:21 ` Waldemar Brodkorb
2016-11-21 23:40 ` Arnout Vandecappelle
2016-11-23 11:37 ` Waldemar Brodkorb [this message]
2016-11-23 12:06 ` Arnout Vandecappelle
2016-11-25 0:26 ` Waldemar Brodkorb
2016-11-21 11:44 ` [Buildroot] [arc-buildroot] " Vlad Zakharov
2016-11-21 14:51 ` Alexey Brodkin
2016-11-21 22:08 ` [Buildroot] " Thomas Petazzoni
2016-11-21 23:38 ` Arnout Vandecappelle
2016-11-22 8:26 ` Thomas Petazzoni
2016-11-22 15:30 ` Arnout Vandecappelle
2016-11-22 15:38 ` Thomas Petazzoni
[not found] ` <CANLo3Ji8MiH29tYCwmpu4KMDJkcm7-75EUGK1mq3e8Tnih6aZQ@mail.gmail.com>
2016-11-22 19:08 ` Romain Naour
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=20161123113702.GZ27313@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@busybox.net \
/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