[Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09

All of lore.kernel.org
 help / color / mirror / Atom feed

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09
@ 2014-05-10  6:30 Thomas Petazzoni
  2014-05-10 20:06 ` Arnout Vandecappelle
  0 siblings, 1 reply; 9+ messages in thread
From: Thomas Petazzoni @ 2014-05-10  6:30 UTC (permalink / raw)
  To: buildroot

Build statistics for 2014-05-09
===============================

        success : 68 
       failures : 41 
       timeouts : 0  
          TOTAL : 109

Classification of failures by reason
====================================

              qdecoder-r12.0.5 | 11
                protobuf-2.5.0 | 9 
           host-protobuf-2.5.0 | 4 
                elfutils-0.155 | 2 
                  cppcms-1.0.4 | 2 
                libmpeg2-0.5.1 | 1 
jack2-ab409a65df95bc261ff72... | 1 
    libcec-libcec-2.1.4-repack | 1 
                    gpm-1.20.7 | 1 
               alsa-lib-1.0.26 | 1 
           imagemagick-6.8.9-0 | 1 
                   slang-2.2.4 | 1 
             lttng-tools-2.4.1 | 1 
libwebsockets-v1.23-chrome3... | 1 
                libsigc-2.2.11 | 1 
                 libpfm4-4.3.0 | 1 
                 cairo-1.12.10 | 1 
          glibc-2.18-svnr23787 | 1 

Detail of failures
===================

   powerpc |                alsa-lib-1.0.26 | NOK | http://autobuild.buildroot.net/results/3a72d567a4c26fa374af5c9a5b1644362a2f74a5/
       arm |                  cairo-1.12.10 | NOK | http://autobuild.buildroot.net/results/2f80e55fe50c32590cdab9475daf54d96d501268/
      bfin |                   cppcms-1.0.4 | NOK | http://autobuild.buildroot.net/results/bbc9e3da31eb38e7614fc47da5821a831bedc1f1/
     avr32 |                   cppcms-1.0.4 | NOK | http://autobuild.buildroot.net/results/016aa51b91e6dca69a830f518d2787772b799673/
      bfin |                 elfutils-0.155 | NOK | http://autobuild.buildroot.net/results/87c55e8a05871ebc326e17f11c3e7f0418a4b6b2/
      bfin |                 elfutils-0.155 | NOK | http://autobuild.buildroot.net/results/8bc659f962379c22ea7896cd05627347fd2e6f4d/
   aarch64 |           glibc-2.18-svnr23787 | NOK | http://autobuild.buildroot.net/results/0f4df1aedfaff75fbbf3e2611884100780c7726f/
microblazeel |                     gpm-1.20.7 | NOK | http://autobuild.buildroot.net/results/d9a7cd7228a80c60489a5c7f9ef4525ccb2400ec/
      i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/cc7873842959a5ba3222c9e70e8b1513d8936d71/
      i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/73811fc73253aecec5560ebf5ccfa52e28e01d6a/
      i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/0d1b1baff85de54902d9c07ff41913f49d89042b/
      i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/11b92a8fec6aae0839ece48b2ed5e58a159f24c5/
       arm |            imagemagick-6.8.9-0 | NOK | http://autobuild.buildroot.net/results/1532fdd30128a606df9f40dfd8092865300a1615/
  mips64el | jack2-ab409a65df95bc261ff72... | NOK | http://autobuild.buildroot.net/results/f3cd51c35067468074039d299581b12d701af7e3/
      bfin |     libcec-libcec-2.1.4-repack | NOK | http://autobuild.buildroot.net/results/1dcf0fd573abb1137c45d97ee4545bb610592434/
   powerpc |                 libmpeg2-0.5.1 | NOK | http://autobuild.buildroot.net/results/99125ec556c386b8795f5fc5c5d255f8ef0c7fbd/
       arc |                  libpfm4-4.3.0 | NOK | http://autobuild.buildroot.net/results/b9c6dab9ed0f8b2fd0f1a2008c3a8fe7a4360123/
     avr32 |                 libsigc-2.2.11 | NOK | http://autobuild.buildroot.net/results/9736db34c946d4a820aae660e8d0afaf15c7eac2/
      bfin | libwebsockets-v1.23-chrome3... | NOK | http://autobuild.buildroot.net/results/961f31463c0acf8c8bd33bfd7f535bf24b0cb494/
       arm |              lttng-tools-2.4.1 | NOK | http://autobuild.buildroot.net/results/27fbb934dba686d44ac2afc4e62be368a3ef00b9/
    xtensa |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/ae9fa612d0b6c9d593504206d5cedd480ad2547e/
   powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/2606a545b3962eebe1331fed701552c2b3dbe097/
       sh4 |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/bcdd448b364dbca32779491fe4535dd04d61e411/
   powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/4d2aea1cdd7f40ab606382210fea5843ae72fea4/
  mips64el |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/f906d803473e99decf75928b18ff63a90bb1e41f/
   powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/2d7502dded4e1dee6fa152183ce170e9cce81cbd/
   powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/4c3ab411e5f2a7acb68197548742de0bea2571ec/
   powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/3a0d5224e8804ea1c4fb158d47b1dc61f9c4bae9/
      mips |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/78c6071f1c49440b9e7bf192867c209885ccedd5/
       arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/bb68a5f845c6750d19a28f06a31ceb7b1f667f30/
       arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/906f8e43ca4464929142d84b955b5461c8683130/
       arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/fae47c457631bc87f026e39bee1be9d73bc7052c/
       arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/b0763ae47a743370937264bacd7cc6f437ad8c8e/
   powerpc |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/ce80256b12bce9f3683fcb266d8b0461f77a93d0/
  mips64el |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/9f1d3a7e8af1ce7a9352ce0aaf2576893dd38364/
    xtensa |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/2cf47321ce71ba70b7ac2f6e65cea01c43f4c5a0/
       arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/f581064492a8c27c42775446130951858eb468cd/
       arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/da8ce760cdabeb9d4cda00dcc801817e4b4eb12c/
       arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/163640270e4fb4e7850fb11cee9faf0d7657d724/
      i486 |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/43ea78c69add490c611e60d05365052077114576/
      bfin |                    slang-2.2.4 | NOK | http://autobuild.buildroot.net/results/97e6cca838cefd48ee91489c6b1914d78da6bf91/


-- 
http://autobuild.buildroot.net

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09
  2014-05-10  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09 Thomas Petazzoni
@ 2014-05-10 20:06 ` Arnout Vandecappelle
  2014-05-11  4:34   ` Baruch Siach
  0 siblings, 1 reply; 9+ messages in thread
From: Arnout Vandecappelle @ 2014-05-10 20:06 UTC (permalink / raw)
  To: buildroot

On 10/05/14 08:30, Thomas Petazzoni wrote:
> Build statistics for 2014-05-09
> ===============================
> 
>         success : 68 
>        failures : 41 
>        timeouts : 0  
>           TOTAL : 109
> 
> Classification of failures by reason
> ====================================
> 
>               qdecoder-r12.0.5 | 11
>                 protobuf-2.5.0 | 9 
>            host-protobuf-2.5.0 | 4 
>                 elfutils-0.155 | 2 
>                   cppcms-1.0.4 | 2 
>                 libmpeg2-0.5.1 | 1 
> jack2-ab409a65df95bc261ff72... | 1 
>     libcec-libcec-2.1.4-repack | 1 
>                     gpm-1.20.7 | 1 
>                alsa-lib-1.0.26 | 1 
>            imagemagick-6.8.9-0 | 1 
>                    slang-2.2.4 | 1 
>              lttng-tools-2.4.1 | 1 
> libwebsockets-v1.23-chrome3... | 1 
>                 libsigc-2.2.11 | 1 
>                  libpfm4-4.3.0 | 1 
>                  cairo-1.12.10 | 1 
>           glibc-2.18-svnr23787 | 1 
> 
> Detail of failures
> ===================
> 
>    powerpc |                alsa-lib-1.0.26 | NOK | http://autobuild.buildroot.net/results/3a72d567a4c26fa374af5c9a5b1644362a2f74a5/
>        arm |                  cairo-1.12.10 | NOK | http://autobuild.buildroot.net/results/2f80e55fe50c32590cdab9475daf54d96d501268/
>       bfin |                   cppcms-1.0.4 | NOK | http://autobuild.buildroot.net/results/bbc9e3da31eb38e7614fc47da5821a831bedc1f1/
>      avr32 |                   cppcms-1.0.4 | NOK | http://autobuild.buildroot.net/results/016aa51b91e6dca69a830f518d2787772b799673/
>       bfin |                 elfutils-0.155 | NOK | http://autobuild.buildroot.net/results/87c55e8a05871ebc326e17f11c3e7f0418a4b6b2/
>       bfin |                 elfutils-0.155 | NOK | http://autobuild.buildroot.net/results/8bc659f962379c22ea7896cd05627347fd2e6f4d/
>    aarch64 |           glibc-2.18-svnr23787 | NOK | http://autobuild.buildroot.net/results/0f4df1aedfaff75fbbf3e2611884100780c7726f/
> microblazeel |                     gpm-1.20.7 | NOK | http://autobuild.buildroot.net/results/d9a7cd7228a80c60489a5c7f9ef4525ccb2400ec/
>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/cc7873842959a5ba3222c9e70e8b1513d8936d71/
>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/73811fc73253aecec5560ebf5ccfa52e28e01d6a/
>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/0d1b1baff85de54902d9c07ff41913f49d89042b/
>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/11b92a8fec6aae0839ece48b2ed5e58a159f24c5/

 This one is on the powerpc autobuilders; it reports:

In file included from ./google/protobuf/stubs/atomicops.h:59:0,
                 from google/protobuf/stubs/atomicops_internals_x86_gcc.cc:36:
./google/protobuf/stubs/platform_macros.h:61:2: error: #error Host architecture
was not detected as supported by protobuf

The weird thing is that the header file has:

#elif defined(__ppc__)
#define GOOGLE_PROTOBUF_ARCH_PPC 1
#define GOOGLE_PROTOBUF_ARCH_32_BIT 1
#else
#error Host architecture was not detected as supported by protobuf
#endif


 So why is __ppc__ not defined?

 Note that it will still fail anyway, because in atomicops.h, there seems to be
no powerpc support.

 I guess that means that protobuf should be blacklisted?

>        arm |            imagemagick-6.8.9-0 | NOK | http://autobuild.buildroot.net/results/1532fdd30128a606df9f40dfd8092865300a1615/
>   mips64el | jack2-ab409a65df95bc261ff72... | NOK | http://autobuild.buildroot.net/results/f3cd51c35067468074039d299581b12d701af7e3/
>       bfin |     libcec-libcec-2.1.4-repack | NOK | http://autobuild.buildroot.net/results/1dcf0fd573abb1137c45d97ee4545bb610592434/
>    powerpc |                 libmpeg2-0.5.1 | NOK | http://autobuild.buildroot.net/results/99125ec556c386b8795f5fc5c5d255f8ef0c7fbd/
>        arc |                  libpfm4-4.3.0 | NOK | http://autobuild.buildroot.net/results/b9c6dab9ed0f8b2fd0f1a2008c3a8fe7a4360123/
>      avr32 |                 libsigc-2.2.11 | NOK | http://autobuild.buildroot.net/results/9736db34c946d4a820aae660e8d0afaf15c7eac2/
>       bfin | libwebsockets-v1.23-chrome3... | NOK | http://autobuild.buildroot.net/results/961f31463c0acf8c8bd33bfd7f535bf24b0cb494/
>        arm |              lttng-tools-2.4.1 | NOK | http://autobuild.buildroot.net/results/27fbb934dba686d44ac2afc4e62be368a3ef00b9/
>     xtensa |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/ae9fa612d0b6c9d593504206d5cedd480ad2547e/
>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/2606a545b3962eebe1331fed701552c2b3dbe097/
>        sh4 |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/bcdd448b364dbca32779491fe4535dd04d61e411/
>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/4d2aea1cdd7f40ab606382210fea5843ae72fea4/
>   mips64el |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/f906d803473e99decf75928b18ff63a90bb1e41f/
>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/2d7502dded4e1dee6fa152183ce170e9cce81cbd/
>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/4c3ab411e5f2a7acb68197548742de0bea2571ec/
>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/3a0d5224e8804ea1c4fb158d47b1dc61f9c4bae9/
>       mips |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/78c6071f1c49440b9e7bf192867c209885ccedd5/

 All these architectures are not supported by the atomicops.

 I'll cook a patch.


 Regards,
 Arnout


>        arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/bb68a5f845c6750d19a28f06a31ceb7b1f667f30/
>        arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/906f8e43ca4464929142d84b955b5461c8683130/
>        arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/fae47c457631bc87f026e39bee1be9d73bc7052c/
>        arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/b0763ae47a743370937264bacd7cc6f437ad8c8e/
>    powerpc |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/ce80256b12bce9f3683fcb266d8b0461f77a93d0/
>   mips64el |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/9f1d3a7e8af1ce7a9352ce0aaf2576893dd38364/
>     xtensa |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/2cf47321ce71ba70b7ac2f6e65cea01c43f4c5a0/
>        arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/f581064492a8c27c42775446130951858eb468cd/
>        arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/da8ce760cdabeb9d4cda00dcc801817e4b4eb12c/
>        arm |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/163640270e4fb4e7850fb11cee9faf0d7657d724/
>       i486 |               qdecoder-r12.0.5 | NOK | http://autobuild.buildroot.net/results/43ea78c69add490c611e60d05365052077114576/
>       bfin |                    slang-2.2.4 | NOK | http://autobuild.buildroot.net/results/97e6cca838cefd48ee91489c6b1914d78da6bf91/
> 
> 


-- 
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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09
  2014-05-10 20:06 ` Arnout Vandecappelle
@ 2014-05-11  4:34   ` Baruch Siach
  2014-05-11 14:42     ` Arnout Vandecappelle
  0 siblings, 1 reply; 9+ messages in thread
From: Baruch Siach @ 2014-05-11  4:34 UTC (permalink / raw)
  To: buildroot

Hi Arnout,

On Sat, May 10, 2014 at 10:06:09PM +0200, Arnout Vandecappelle wrote:
> >       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/cc7873842959a5ba3222c9e70e8b1513d8936d71/
> >       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/73811fc73253aecec5560ebf5ccfa52e28e01d6a/
> >       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/0d1b1baff85de54902d9c07ff41913f49d89042b/
> >       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/11b92a8fec6aae0839ece48b2ed5e58a159f24c5/
> 
>  This one is on the powerpc autobuilders; it reports:
> 
> In file included from ./google/protobuf/stubs/atomicops.h:59:0,
>                  from google/protobuf/stubs/atomicops_internals_x86_gcc.cc:36:
> ./google/protobuf/stubs/platform_macros.h:61:2: error: #error Host architecture
> was not detected as supported by protobuf
> 
> The weird thing is that the header file has:
> 
> #elif defined(__ppc__)
> #define GOOGLE_PROTOBUF_ARCH_PPC 1
> #define GOOGLE_PROTOBUF_ARCH_32_BIT 1
> #else
> #error Host architecture was not detected as supported by protobuf
> #endif
> 
>  So why is __ppc__ not defined?

It's __PPC__ on toolchains I have access to.

>  Note that it will still fail anyway, because in atomicops.h, there seems to 
>  be no powerpc support.

Correct. As I mentioned at http://patchwork.ozlabs.org/patch/347044/, the 
patch from http://code.google.com/p/protobuf/issues/detail?id=488 adds powerpc 
support, but it uses gcc internal atomic operations, so it is only applicable 
to gcc 4.7+.

>  I guess that means that protobuf should be blacklisted?

Probably.

> >     xtensa |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/ae9fa612d0b6c9d593504206d5cedd480ad2547e/
> >    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/2606a545b3962eebe1331fed701552c2b3dbe097/
> >        sh4 |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/bcdd448b364dbca32779491fe4535dd04d61e411/
> >    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/4d2aea1cdd7f40ab606382210fea5843ae72fea4/
> >   mips64el |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/f906d803473e99decf75928b18ff63a90bb1e41f/
> >    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/2d7502dded4e1dee6fa152183ce170e9cce81cbd/
> >    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/4c3ab411e5f2a7acb68197548742de0bea2571ec/
> >    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/3a0d5224e8804ea1c4fb158d47b1dc61f9c4bae9/
> >       mips |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/78c6071f1c49440b9e7bf192867c209885ccedd5/
> 
>  All these architectures are not supported by the atomicops.
> 
>  I'll cook a patch.

Your patch is correct, I guess, but as far as I understand it doesn't solve 
the host architecture dependency problem that is causing the host-protobuf 
failure above.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09
  2014-05-11  4:34   ` Baruch Siach
@ 2014-05-11 14:42     ` Arnout Vandecappelle
  2014-05-11 14:55       ` Baruch Siach
                         ` (2 more replies)
  0 siblings, 3 replies; 9+ messages in thread
From: Arnout Vandecappelle @ 2014-05-11 14:42 UTC (permalink / raw)
  To: buildroot

On 11/05/14 06:34, Baruch Siach wrote:
> Hi Arnout,
> 
> On Sat, May 10, 2014 at 10:06:09PM +0200, Arnout Vandecappelle wrote:
>>>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/cc7873842959a5ba3222c9e70e8b1513d8936d71/
>>>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/73811fc73253aecec5560ebf5ccfa52e28e01d6a/
>>>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/0d1b1baff85de54902d9c07ff41913f49d89042b/
>>>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/11b92a8fec6aae0839ece48b2ed5e58a159f24c5/
>>
>>  This one is on the powerpc autobuilders; it reports:
>>
>> In file included from ./google/protobuf/stubs/atomicops.h:59:0,
>>                  from google/protobuf/stubs/atomicops_internals_x86_gcc.cc:36:
>> ./google/protobuf/stubs/platform_macros.h:61:2: error: #error Host architecture
>> was not detected as supported by protobuf
>>
>> The weird thing is that the header file has:
>>
>> #elif defined(__ppc__)
>> #define GOOGLE_PROTOBUF_ARCH_PPC 1
>> #define GOOGLE_PROTOBUF_ARCH_32_BIT 1
>> #else
>> #error Host architecture was not detected as supported by protobuf
>> #endif
>>
>>  So why is __ppc__ not defined?
> 
> It's __PPC__ on toolchains I have access to.
> 
>>  Note that it will still fail anyway, because in atomicops.h, there seems to 
>>  be no powerpc support.
> 
> Correct. As I mentioned at http://patchwork.ozlabs.org/patch/347044/, the 
> patch from http://code.google.com/p/protobuf/issues/detail?id=488 adds powerpc 
> support, but it uses gcc internal atomic operations, so it is only applicable 
> to gcc 4.7+.

 But that patch still checks the architecture, and it only adds aarch64 and ppc
support...

> 
>>  I guess that means that protobuf should be blacklisted?
> 
> Probably.
> 
>>>     xtensa |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/ae9fa612d0b6c9d593504206d5cedd480ad2547e/
>>>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/2606a545b3962eebe1331fed701552c2b3dbe097/
>>>        sh4 |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/bcdd448b364dbca32779491fe4535dd04d61e411/
>>>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/4d2aea1cdd7f40ab606382210fea5843ae72fea4/
>>>   mips64el |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/f906d803473e99decf75928b18ff63a90bb1e41f/
>>>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/2d7502dded4e1dee6fa152183ce170e9cce81cbd/
>>>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/4c3ab411e5f2a7acb68197548742de0bea2571ec/
>>>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/3a0d5224e8804ea1c4fb158d47b1dc61f9c4bae9/
>>>       mips |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/78c6071f1c49440b9e7bf192867c209885ccedd5/
>>
>>  All these architectures are not supported by the atomicops.
>>
>>  I'll cook a patch.
> 
> Your patch is correct, I guess, but as far as I understand it doesn't solve 
> the host architecture dependency problem that is causing the host-protobuf 
> failure above.

 True. We could add a dependency on BR2_HOSTARCH for that. Except that Kconfig
doesn't support string comparison AFAIK. So we'd need to create bool symbols for
all the supported host architectures...


 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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09
  2014-05-11 14:42     ` Arnout Vandecappelle
@ 2014-05-11 14:55       ` Baruch Siach
  2014-05-11 20:41         ` Arnout Vandecappelle
  2014-05-11 16:00       ` Yann E. MORIN
  2014-05-11 22:03       ` Thomas Petazzoni
  2 siblings, 1 reply; 9+ messages in thread
From: Baruch Siach @ 2014-05-11 14:55 UTC (permalink / raw)
  To: buildroot

Hi Arnout,

On Sun, May 11, 2014 at 04:42:54PM +0200, Arnout Vandecappelle wrote:
> On 11/05/14 06:34, Baruch Siach wrote:
> > On Sat, May 10, 2014 at 10:06:09PM +0200, Arnout Vandecappelle wrote:
> >>>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/cc7873842959a5ba3222c9e70e8b1513d8936d71/
> >>>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/73811fc73253aecec5560ebf5ccfa52e28e01d6a/
> >>>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/0d1b1baff85de54902d9c07ff41913f49d89042b/
> >>>       i686 |            host-protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/11b92a8fec6aae0839ece48b2ed5e58a159f24c5/
> >>
> >>  This one is on the powerpc autobuilders; it reports:
> >>
> >> In file included from ./google/protobuf/stubs/atomicops.h:59:0,
> >>                  from google/protobuf/stubs/atomicops_internals_x86_gcc.cc:36:
> >> ./google/protobuf/stubs/platform_macros.h:61:2: error: #error Host architecture
> >> was not detected as supported by protobuf
> >>
> >> The weird thing is that the header file has:
> >>
> >> #elif defined(__ppc__)
> >> #define GOOGLE_PROTOBUF_ARCH_PPC 1
> >> #define GOOGLE_PROTOBUF_ARCH_32_BIT 1
> >> #else
> >> #error Host architecture was not detected as supported by protobuf
> >> #endif
> >>
> >>  So why is __ppc__ not defined?
> > 
> > It's __PPC__ on toolchains I have access to.
> > 
> >>  Note that it will still fail anyway, because in atomicops.h, there seems to 
> >>  be no powerpc support.
> > 
> > Correct. As I mentioned at http://patchwork.ozlabs.org/patch/347044/, the 
> > patch from http://code.google.com/p/protobuf/issues/detail?id=488 adds powerpc 
> > support, but it uses gcc internal atomic operations, so it is only applicable 
> > to gcc 4.7+.
> 
>  But that patch still checks the architecture, and it only adds aarch64 and ppc
> support...
> 
> > 
> >>  I guess that means that protobuf should be blacklisted?
> > 
> > Probably.
> > 
> >>>     xtensa |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/ae9fa612d0b6c9d593504206d5cedd480ad2547e/
> >>>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/2606a545b3962eebe1331fed701552c2b3dbe097/
> >>>        sh4 |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/bcdd448b364dbca32779491fe4535dd04d61e411/
> >>>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/4d2aea1cdd7f40ab606382210fea5843ae72fea4/
> >>>   mips64el |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/f906d803473e99decf75928b18ff63a90bb1e41f/
> >>>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/2d7502dded4e1dee6fa152183ce170e9cce81cbd/
> >>>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/4c3ab411e5f2a7acb68197548742de0bea2571ec/
> >>>    powerpc |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/3a0d5224e8804ea1c4fb158d47b1dc61f9c4bae9/
> >>>       mips |                 protobuf-2.5.0 | NOK | http://autobuild.buildroot.net/results/78c6071f1c49440b9e7bf192867c209885ccedd5/
> >>
> >>  All these architectures are not supported by the atomicops.
> >>
> >>  I'll cook a patch.
> > 
> > Your patch is correct, I guess, but as far as I understand it doesn't solve 
> > the host architecture dependency problem that is causing the host-protobuf 
> > failure above.
> 
>  True. We could add a dependency on BR2_HOSTARCH for that. Except that Kconfig
> doesn't support string comparison AFAIK. So we'd need to create bool symbols for
> all the supported host architectures...

How would that solve the problem? Host packages are selected directly from 
Makefiles, regardless of Kconfig settings, isn't it? Or do you intend to add 
host architecture dependencies to all reverse dependencies of host-protobuf 
(currently: protobuf-c, protobuf, python-protobuf, and their reverse 
dependencies)?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09
  2014-05-11 14:55       ` Baruch Siach
@ 2014-05-11 20:41         ` Arnout Vandecappelle
  2014-05-11 20:47           ` Peter Korsgaard
  0 siblings, 1 reply; 9+ messages in thread
From: Arnout Vandecappelle @ 2014-05-11 20:41 UTC (permalink / raw)
  To: buildroot

On 11/05/14 16:55, Baruch Siach wrote:
> Hi Arnout,
> 
> On Sun, May 11, 2014 at 04:42:54PM +0200, Arnout Vandecappelle wrote:
>> On 11/05/14 06:34, Baruch Siach wrote:
[snip]
>>> Your patch is correct, I guess, but as far as I understand it doesn't solve 
>>> the host architecture dependency problem that is causing the host-protobuf 
>>> failure above.
>>
>>  True. We could add a dependency on BR2_HOSTARCH for that. Except that Kconfig
>> doesn't support string comparison AFAIK. So we'd need to create bool symbols for
>> all the supported host architectures...
> 
> How would that solve the problem? Host packages are selected directly from 
> Makefiles, regardless of Kconfig settings, isn't it? Or do you intend to add 
> host architecture dependencies to all reverse dependencies of host-protobuf 
> (currently: protobuf-c, protobuf, python-protobuf, and their reverse 
> dependencies)?

 Exactly. But I don't really think it's worthwhile to do that - except for the
autobuilder, there is probably nobody who tries building on anything except x86.

 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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09
  2014-05-11 20:41         ` Arnout Vandecappelle
@ 2014-05-11 20:47           ` Peter Korsgaard
  0 siblings, 0 replies; 9+ messages in thread
From: Peter Korsgaard @ 2014-05-11 20:47 UTC (permalink / raw)
  To: buildroot

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

Hi,

 >> How would that solve the problem? Host packages are selected directly from 
 >> Makefiles, regardless of Kconfig settings, isn't it? Or do you intend to add 
 >> host architecture dependencies to all reverse dependencies of host-protobuf 
 >> (currently: protobuf-c, protobuf, python-protobuf, and their reverse 
 >> dependencies)?

 >  Exactly. But I don't really think it's worthwhile to do that - except for the
 > autobuilder, there is probably nobody who tries building on anything except x86.

Indeed. I don't think the host-protobuf issue is something anybody will
run into in reality.

-- 
Bye, Peter Korsgaard

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09
  2014-05-11 14:42     ` Arnout Vandecappelle
  2014-05-11 14:55       ` Baruch Siach
@ 2014-05-11 16:00       ` Yann E. MORIN
  2014-05-11 22:03       ` Thomas Petazzoni
  2 siblings, 0 replies; 9+ messages in thread
From: Yann E. MORIN @ 2014-05-11 16:00 UTC (permalink / raw)
  To: buildroot

Arnout, All,

On 2014-05-11 16:42 +0200, Arnout Vandecappelle spake thusly:
>  True. We could add a dependency on BR2_HOSTARCH for that. Except that Kconfig
> doesn't support string comparison AFAIK.

He, yes it does:

    config FOO
        string "foo"

    config BAR
        string "bar"

    config EQ
        default y if FOO = BAR

Now, try to set FOO="whatever" and BAR="whatever" and look at the
resulting .config file. ;-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09
  2014-05-11 14:42     ` Arnout Vandecappelle
  2014-05-11 14:55       ` Baruch Siach
  2014-05-11 16:00       ` Yann E. MORIN
@ 2014-05-11 22:03       ` Thomas Petazzoni
  2 siblings, 0 replies; 9+ messages in thread
From: Thomas Petazzoni @ 2014-05-11 22:03 UTC (permalink / raw)
  To: buildroot

Dear Arnout Vandecappelle,

On Sun, 11 May 2014 16:42:54 +0200, Arnout Vandecappelle wrote:

> > Your patch is correct, I guess, but as far as I understand it doesn't solve 
> > the host architecture dependency problem that is causing the host-protobuf 
> > failure above.
> 
>  True. We could add a dependency on BR2_HOSTARCH for that. Except that Kconfig
> doesn't support string comparison AFAIK. So we'd need to create bool symbols for
> all the supported host architectures...

We already use string comparison in quite a few places, especially in
toolchain/toolchain-external/Config.in:

	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2014-05-11 22:03 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-05-10  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-09 Thomas Petazzoni
2014-05-10 20:06 ` Arnout Vandecappelle
2014-05-11  4:34   ` Baruch Siach
2014-05-11 14:42     ` Arnout Vandecappelle
2014-05-11 14:55       ` Baruch Siach
2014-05-11 20:41         ` Arnout Vandecappelle
2014-05-11 20:47           ` Peter Korsgaard
2014-05-11 16:00       ` Yann E. MORIN
2014-05-11 22:03       ` Thomas Petazzoni

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.