public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ARM] [STATUS] **NO** Increasingly high build failures
Date: Thu, 19 Apr 2012 13:54:54 +0200	[thread overview]
Message-ID: <4F8FFD0E.60104@aribaud.net> (raw)
In-Reply-To: <4F8FE335.2050609@aribaud.net>

Le 19/04/2012 12:04, Albert ARIBAUD a ?crit :
> Hi Wolfgang,
>
> Le 19/04/2012 11:51, Wolfgang Denk a ?crit :
>> Dear Albert ARIBAUD,
>>
>> In message<4F8FBB22.5000205@aribaud.net> you wrote:
>>> Folks,
>>>
>>> I just did another round of ./MAKEALL arm with MG/CS 2011.09-69, and the
>>> failure rate is rising to say the least, with 277 boards failing out of
>>> 278. :(
>>
>> Which version of GCC is this?
>>
>> Recent tests with ELDK 5.2 (which is based on gcc version 4.6.4
>> 20120303) show no such problems.
>>
>> Best regards,
>>
>> Wolfgang Denk
>
> Seems there was a misconfiguration in my toolchain and repo -- redoing
> the mass build with correct settings, will update notice when done

After triple-checking the I was using the right commit (my current 
master) and the right toolchain ("gcc version 4.6.1 (Sourcery CodeBench 
Lite 2011.09-69)"), ./MAKEALL arm shows the following:

--------------------- SUMMARY ----------------------------
Boards compiled: 277
Boards with warnings or errors: 28 ( VCMA9 smdk2410 nhk8815 
nhk8815_onenand apollon igep0020 igep0030 omap4_panda omap4_sdp4430 
omap5_evm s5p_goni smdkc100 s5pc210_universal seaboard ventana balloon3 
lubbock palmld palmtc polaris pxa255_idp trizepsiv vpac270_nor_128 
vpac270_nor_256 vpac270_ond_256 xaeniax zipitz2 colibri_pxa270 )
----------------------------------------------------------

... with still 3 build errors, for omap4_panda, omap4_sdp4430 and 
omap5_evm: 'internal compiler error: in decode_addr_const, at 
varasm.c:2635', and 57 warnings of which 48 are 'uses variable-size 
enums yet the output is to use 32-bit enums' and 9 are 'variable [...] 
set but not used [-Wunused-but-set-variable]'

So the only 'issue' is the enums, for which I'll seek a solution.

Apologies -- especially to Simon G.* -- for the noise.

Amicalement,
-- 
Albert.

  reply	other threads:[~2012-04-19 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19  7:13 [U-Boot] [ARM] [STATUS] Increasingly high build failures Albert ARIBAUD
2012-04-19  9:51 ` Wolfgang Denk
2012-04-19 10:04   ` Albert ARIBAUD
2012-04-19 11:54     ` Albert ARIBAUD [this message]
2012-04-19 13:06       ` [U-Boot] [ARM] [STATUS] **NO** " Wolfgang Denk
2012-04-19 17:23 ` [U-Boot] [ARM] [STATUS] " Simon Glass

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=4F8FFD0E.60104@aribaud.net \
    --to=albert.u.boot@aribaud.net \
    --cc=u-boot@lists.denx.de \
    /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