Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-04-07
Date: Thu, 12 Apr 2018 16:37:37 +0200	[thread overview]
Message-ID: <20180412163737.16e4b8e1@windsurf> (raw)
In-Reply-To: <1285703624.2923407.1523543239898.JavaMail.zimbra@datacom.ind.br>

Hello,

On Thu, 12 Apr 2018 11:27:19 -0300 (BRT), Carlos Santos wrote:

> I generated toolchains with ct-NG 1.20 for i686 and ARM. Here are
> the results:
> 
> $ i686-nptl-linux-gnu-gcc --version
> i686-nptl-linux-gnu-gcc (crosstool-NG 1.20.0) 4.7.4
> $ echo '#include <glib-object.h>' | i686-nptl-linux-gnu-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 <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
> 
> $ arm-unknown-linux-gnueabi-gcc --version
> arm-unknown-linux-gnueabi-gcc (crosstool-NG 1.20.0) 4.7.4
> $ echo '#include <glib-object.h>' | arm-unknown-linux-gnueabi-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 <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

So the problem is indeed not PowerPC specific :) Thanks for taking the
time to generate those toolchains BTW!

Perhaps this will encourage the glib developers to accept a solution
upstream ?

> I will change in the tpm2-abrmd recipe but will try to restrict it to
> GCC 4.7.x and below.

What about a solution in glib itself ? Make those definitions
conditional on the gcc version, i.e only if gcc >= 4.8 is used ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-04-12 14:37 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 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-04-07 Carlos Santos
2018-04-10  3:00   ` 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 [this message]
     [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=20180412163737.16e4b8e1@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --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