Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-07-29
Date: Sun, 31 Jul 2016 14:44:25 +0200	[thread overview]
Message-ID: <9e817dxthf.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20160730232322.4eca1a53@free-electrons.com

Hi Thomas,

Am Sat, 30 Jul 2016 23:23:22 +0200 schrieb Thomas Petazzoni:

>>          arm | inotify-tools-1df9af4d6cd0f... | NOK | http://autobuild.buildroot.net/results/abcaf70523863a4cd096a1b063be2e742355849f/
> 
> inotifywait.c: In function 'output_event_csv':
> inotifywait.c:126:5: error: this 'if' clause does not guard... [-Werror=misleading-indentation]
>      if (filename != NULL)
> 
> gcc 6.x build issue. Bernd, you are the last person who bumped this
> package. Could you investigate?

sent patch: http://patchwork.ozlabs.org/patch/654313/

>>          arm |              libsidplay2-2.1.1 | NOK | http://autobuild.buildroot.net/results/8907e367345ac8ec16f118eb550810b4e758f0c3/
> 
> xsid.cpp:101:1: error: narrowing conversion of ''\200'' from 'char' to 'int8_t {aka signed char}' inside { } [-Wnarrowing]
>  };
>  ^
> xsid.cpp:101:1: error: narrowing conversion of ''\224'' from 'char' to 'int8_t {aka signed char}' inside { } [-Wnarrowing]
> xsid.cpp:101:1: error: narrowing conversion of ''\251'' from 'char' to 'int8_t {aka signed char}' inside { } [-Wnarrowing]
> xsid.cpp:101:1: error: narrowing conversion of ''\274'' from 'char' to 'int8_t {aka signed char}' inside { } [-Wnarrowing]
> xsid.cpp:101:1: error: narrowing conversion of ''\316'' from 'char' to 'int8_t {aka signed char}' inside { } [-Wnarrowing]
> xsid.cpp:101:1: error: narrowing conversion of ''\341'' from 'char' to 'int8_t {aka signed char}' inside { } [-Wnarrowing]
> xsid.cpp:101:1: error: narrowing conversion of ''\362'' from 'char' to 'int8_t {aka signed char}' inside { } [-Wnarrowing]
> 
> Bernd, this is your package.

Need to investigate more, but I am unsure whether I can fix
the bug with my limited C++ skills.

>>          arm |                   libvpx-1.4.0 | NOK | http://autobuild.buildroot.net/results/39e39de374414ffa07b6dc5f25c39dfb47cc8ad4/
> 
> ./vpx_mem/vpx_mem.h:17:19: fatal error: lddk.h: No such file or directory
> 
> Bernd ?

Sent patch: http://patchwork.ozlabs.org/patch/654323/
Most buildroot toolchains do not define __uClinux_, those who
do trigger the bug.

>>          arm |                openswan-2.6.46 | NOK | http://autobuild.buildroot.net/results/70da34c1528b51e92e9e60788f83733d70b33353/
> 
> In file included from /home/buildroot/autobuild/run/instance-2/output/build/openswan-2.6.46/lib/libopenswan/constants.c:1361:0:
> /home/buildroot/autobuild/run/instance-2/output/build/openswan-2.6.46/include/arpa/nameser.h:58:23: fatal error: sys/cdefs.h: No such file or directory
>  #include <sys/cdefs.h>
> 
> musl issue. Bernd, or Gustavo, you are the last ones who bumped this
> package, could you have a look?

Sent patch: http://patchwork.ozlabs.org/patch/654336/

>>      powerpc |              transmission-2.92 | NOK | http://autobuild.buildroot.net/results/12184cde82a405eb41356ce88918b2f28bc5c237/
> 
> net.c:40:24: fatal error: libutp/utp.h: No such file or directory
> 
> Bernd ?

Sent patch v2: http://patchwork.ozlabs.org/patch/654343/

>>     mips64el |     xserver_xorg-server-1.18.4 | NOK | http://autobuild.buildroot.net/results/349fb43101d4e780203baea1dac7ff4189bc28bb/
> 
> Bernd, this one is for you. I know you already sent a patch for this,
> which I didn't like. Do you think you will have some time to rework
> this patch?

Sent patch: http://patchwork.ozlabs.org/patch/654357/

Regards, Bernd

  parent reply	other threads:[~2016-07-31 12:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-30  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-07-29 Thomas Petazzoni
2016-07-30 21:23 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-07-31  7:44   ` Peter Korsgaard
2016-07-31  8:48   ` Waldemar Brodkorb
2016-07-31 12:44   ` Bernd Kuhls [this message]
2016-08-04  8:12     ` Khem Raj
2016-07-31 18:56   ` Baruch Siach
2016-07-31 20:56     ` Thomas Petazzoni
2016-07-31 20:06   ` Romain Naour
2016-07-31 20:49     ` Romain Naour
2016-07-31 21:42     ` Waldemar Brodkorb
2016-07-31 21:25   ` Yann E. MORIN
2016-08-01 15:43   ` Vlad Zakharov
     [not found]   ` <CACcFhEWvcokFB0WFsVpv6PaB-5QBnDNvhgSPFGmk43=zq8D6=A@mail.gmail.com>
2016-08-02  7:19     ` Thomas Petazzoni
2016-08-03  8:27   ` Olivier Schonken
2016-08-03 20:10   ` Angelo Compagnucci
2016-08-03 20:23     ` Yann E. MORIN

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=9e817dxthf.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --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