All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-04-07
Date: Mon, 9 Apr 2018 23:50:27 -0300 (BRT)	[thread overview]
Message-ID: <147906727.2330850.1523328627127.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20180408060016.70C472084F@mail.bootlin.com>

> From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> To: "Carlos Santos" <casantos@datacom.ind.br>
> Sent: Sunday, April 8, 2018 3:00:16 AM
> Subject: [autobuild.buildroot.net] Your build results for 2018-04-07

> Hello,
> 
> This is the list of Buildroot build failures that occured on
> 2018-04-07, and for which you are a registered architecture developer
> or package developer. Please help us improving the quality of
> Buildroot by investigating those build failures and sending patches to
> fix them. Thanks!
> 
> Results for the 'master' branch
> ===============================
> 
> Build failures related to your packages:
> 
>     powerpc |               tpm2-abrmd-1.3.0 |
>     http://autobuild.buildroot.net/results/b29a2f868438a2210873ea72f491db63175848be
> 
> --
> http://autobuild.buildroot.net

The it's a problem libglib2, not in tpm2-abrmd:

$ echo -e '#include <gio/gio.h>\nint main(){return 0;}' | host/bin/powerpc-ctng_e500v2-linux-gnuspe-gcc -x c -I staging/usr/include/glib-2.0 -I staging/usr/lib/glib-2.0/include -Wall -Werror -c - -o /tmp/foo.o
In file included from staging/usr/include/glib-2.0/gobject/gbinding.h:29:0,
                 from staging/usr/include/glib-2.0/glib-object.h:23,
                 from staging/usr/include/glib-2.0/gio/gioenums.h:28,
                 from staging/usr/include/glib-2.0/gio/giotypes.h:28,
                 from staging/usr/include/glib-2.0/gio/gio.h:26,
                 from <stdin>:1:
staging/usr/include/glib-2.0/gobject/gobject.h: In function 'g_set_object':
staging/usr/include/glib-2.0/gobject/gobject.h:725:5: error: value computed is not used [-Werror=unused-value]
cc1: all warnings being treated as errors

This was after commit 4dcfcd17c09b5684e95943de119b95a34c93ad63, so the
bump to libglig2 v2.56.1 did not solve the problem.

-- 
Carlos Santos (Casantos) - DATACOM, P&D
?The greatest triumph that modern PR can offer is the transcendent 
success of having your words and actions judged by your reputation, 
rather than the other way about.? ? Christopher Hitchens

       reply	other threads:[~2018-04-10  2:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180408060016.70C472084F@mail.bootlin.com>
2018-04-10  2:50 ` Carlos Santos [this message]
2018-04-10  3:00   ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-04-07 Carlos Santos
2018-04-10 17:09     ` Fabrice Fontaine
2018-04-10 18:53       ` Fabrice Fontaine
2018-04-11 12:39         ` Carlos Santos
2018-04-11 13:19           ` Thomas Petazzoni
2018-04-12  2:40             ` Carlos Santos
2018-04-12  7:06               ` Thomas Petazzoni
2018-04-12 14:27                 ` Carlos Santos
2018-04-12 14:37                   ` Thomas Petazzoni
     [not found] <20180408060016.A832E207F1@mail.bootlin.com>
2018-04-08 15:09 ` André Hentschel
2018-04-08 15:48   ` 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=147906727.2330850.1523328627127.JavaMail.zimbra@datacom.ind.br \
    --to=casantos@datacom.ind.br \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.