All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Build errors in u-boot mainline and daily builds
Date: Sat, 3 Jan 2009 16:37:49 +0100	[thread overview]
Message-ID: <20090103153749.GC17175@game.jcrosoft.org> (raw)
In-Reply-To: <3efb10970901030310r7cfc1245g97ac0db4375ddc33@mail.gmail.com>

On 12:10 Sat 03 Jan     , Remy Bohmer wrote:
> Hello All,
> 
> I started a server to do only daily builds of all U-boot board
> configurations. (currently on a old slow box, but it works, it takes
> about 2 hours to build all boards for ARM only)
> 
> The primary goal was to find early compile regressions in the
> u-boot-USB tree that I maintain, before pushing patches to mainline.
> To find a regression compared to u-boot mainline, the u-boot mainline
> (master branch) also needs to build, so I build that tree also daily
> from now.
> 
> Currently I only build for ARM based boards, but there is no limit on
> architectures, if I have all the cross-compilers.
> I use the Denx ELDK for ARM as cross-compile toolchain.
> 
> First, I discovered some build failures of which the logging is listed below.
> What can we do about these errors? Are these boards still maintained?
> Should these be fixed? Who wants to fix them?
> I currently run the 'MAKEALL arm' script to build all these boards, so
> either the boards should be fixed, or if no longer maintained removed
> (at least from the MAKEALL script)
I do the same weekly and on patch commit on arm and other arch as ppc, mips, sh4

for ARM I use different toolchains

> 
> Further, is there any interest to make the daily build results public?
> * Is it appreciated if I post the build results in a daily post to the
> mailinglist, _if_ there is a build failure? (No news is good news)
> What format is preferred?
> * Or is it preferred to post the results on a website?
> * Or ...
a mail notice to the custodian will nice on new build issue
and a website

> ------------------------------------------------------------
> Building U-boot:
> * branch: master
> * src-dir: /home/remy/nightbuild/git/u-boot
> ------------------------------------------------------------
> Configuring for m501sk board...
> cpu/arm920t/at91rm9200/libat91rm9200.a(lowlevel_init.o): In function `SMRDATA':
> /home/remy/nightbuild/git/u-boot/cpu/arm920t/at91rm9200/lowlevel_init.S:132:
> undefined reference to `MC_PUIA_VAL'
> /home/remy/nightbuild/git/u-boot/cpu/arm920t/at91rm9200/lowlevel_init.S:132:
> undefined reference to `MC_PUP_VAL'
> /home/remy/nightbuild/git/u-boot/cpu/arm920t/at91rm9200/lowlevel_init.S:132:
> undefined reference to `MC_PUER_VAL'
The problem are already known and I've send patch to fix it just before my vacation

 
> 
> Configuring for actux4 board...
> actux4.c: In function 'board_init':
> actux4.c:83: warning: left shift count >= width of type
> actux4.c:83: warning: left shift count >= width of type
>    text	   data	    bss	    dec	    hex	filename
>  222576	   6692	 550812	 780080	
> be730	/home/remy/nightbuild/scratch/build/u-boot
Known too
> 
> 
> Configuring for ixdp425 board...
> make[1]: *** No rule to make target
> `/home/remy/nightbuild/scratch/build/cpu/ixp/npe/IxNpeMicrocode.o',
> needed by `/home/remy/nightbuild/scratch/build/cpu/ixp/npe/libnpe.a'.
> Stop.
> make: *** [/home/remy/nightbuild/scratch/build/cpu/ixp/npe/libnpe.a] Error 2

we can not add the IxNpeMicrocode.c due to licencing issue
a new way has be commit to allow the FW to be load from flash instead of
built-in

Best Regards,
J.

      parent reply	other threads:[~2009-01-03 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 11:10 [U-Boot] [RFC] Build errors in u-boot mainline and daily builds Remy Bohmer
2009-01-03 11:36 ` Mike Frysinger
2009-01-03 15:18 ` Wolfgang Denk
2009-01-03 17:28   ` Jerry Van Baren
2009-01-03 20:05     ` Remy Bohmer
2009-01-03 20:22       ` Wolfgang Denk
2009-01-03 20:08     ` Wolfgang Denk
2009-01-03 15:37 ` Jean-Christophe PLAGNIOL-VILLARD [this message]

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=20090103153749.GC17175@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --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 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.