From: Angelo Dureghello <angelo@sysam.it>
To: u-boot@lists.denx.de
Subject: [U-Boot] m68k: Build problems on some boards
Date: Tue, 02 Dec 2014 10:22:48 +0100 [thread overview]
Message-ID: <547D84E8.90900@sysam.it> (raw)
In-Reply-To: <20141202132613.67DB.AA925319@jp.panasonic.com>
Dear Masahiro,
>
> I recommend you to use kernel.org toolchain as I mentioned in
> http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/188763/focus=190993
> or
> "git log fbe79a17fddb7f0b"
>
>
many thanks, i am not confident still using the archive, was using the
"pipermail" archive, and clicking "next message" it was not showing
your last message since it was in the next month.
Will use gmane as you did.
And thanks to your post i have also seen now how to build all the m68k
boards in the correct way.
So the tool chain you posted gives no warnings and so it is the
recommended one to be used actually. Will install it tonight.
In any case, i was also able to build all the boards with my current
toolchain:
opt/CodeSourcery/Sourcery_CodeBench_Lite_for_ColdFire_ELF/bin/m68k-elf-gcc
--version
m68k-elf-gcc (Sourcery CodeBench Lite 2011.09-21) 4.6.1
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
--------------------- SUMMARY ----------------------------
Boards compiled: 48
Boards with warnings but no errors: 48 ( M52277EVB M52277EVB_stmicro
M5235EVB M5235EVB_Flash32 cobra5272 eb_cpu5282 eb_cpu5282_internal
TASREG M5208EVBE M5249EVB M5253DEMO M5272C3 M5275EVB M5282EVB
astro_mcf5373l M53017EVB M5329AFEE M5329BFEE M5373EVB M54418TWR
M54418TWR_nand_mii M54418TWR_nand_rmii M54418TWR_nand_rmii_lowfreq
M54418TWR_serial_mii M54418TWR_serial_rmii M54451EVB M54451EVB_stmicro
M54455EVB M54455EVB_a66 M54455EVB_i66 M54455EVB_intel M54455EVB_stm33
M5475AFE M5475BFE M5475CFE M5475DFE M5475EFE M5475FFE M5475GFE M5485AFE
M5485BFE M5485CFE M5485DFE M5485EFE M5485FFE M5485GFE M5485HFE M5253EVBE )
----------------------------------------------------------
But it gives several warnings, more or less the same for each board, i
attach them in case of any use:
Building M54455EVB_stm33 board...
text data bss dec hex filename
174005 13744 221236 408985 63d99 ./u-boot
tools/kwbimage.c: In function ?kwbimage_set_header?:
tools/kwbimage.c:803:8: warning: ?headersz? may be used uninitialized in
this function [-Wmaybe-uninitialized]
memcpy(ptr, image, headersz);
^
common/cli_simple.c: In function 'cli_simple_process_macros':
common/cli_simple.c:73:2: warning: format '%zd' expects argument of type
'signed size_t', but argument 2 has type '__kernel_size_t' [-Wformat]
common/cli_simple.c:162:2: warning: format '%zd' expects argument of
type 'signed size_t', but argument 2 has type '__kernel_size_t' [-Wformat]
drivers/mtd/spi/sf.c: In function 'spi_flash_read_write':
drivers/mtd/spi/sf.c:30:3: warning: format '%zu' expects argument of
type 'size_t', but argument 2 has type 'unsigned int' [-Wformat]
drivers/mtd/spi/sf.c:36:4: warning: format '%zu' expects argument of
type 'size_t', but argument 2 has type 'unsigned int' [-Wformat]
drivers/mtd/spi/sf_ops.c: In function 'spi_flash_cmd_write_ops':
drivers/mtd/spi/sf_ops.c:324:3: warning: format '%zu' expects argument
of type 'size_t', but argument 7 has type 'unsigned int' [-Wformat]
common/cmd_sf.c: In function 'spi_flash_update_block':
common/cmd_sf.c:166:2: warning: format '%zx' expects argument of type
'size_t', but argument 4 has type 'unsigned int' [-Wformat]
common/cmd_sf.c:173:3: warning: format '%zx' expects argument of type
'size_t', but argument 3 has type 'unsigned int' [-Wformat]
common/cmd_sf.c: In function 'spi_flash_update':
common/cmd_sf.c:248:9: warning: format '%zu' expects argument of type
'size_t', but argument 2 has type 'unsigned int' [-Wformat]
common/cmd_sf.c:248:9: warning: format '%zu' expects argument of type
'size_t', but argument 3 has type 'unsigned int' [-Wformat]
common/cmd_sf.c: In function 'do_spi_flash_read_write':
common/cmd_sf.c:303:10: warning: format '%zu' expects argument of type
'size_t', but argument 2 has type 'unsigned int' [-Wformat]
common/cmd_sf.c: In function 'do_spi_flash_erase':
common/cmd_sf.c:338:9: warning: format '%zu' expects argument of type
'size_t', but argument 2 has type 'unsigned int' [-Wformat]
common/cmd_nvedit.c: In function 'do_env_export':
common/cmd_nvedit.c:914:3: warning: format '%zX' expects argument of
type 'size_t', but argument 3 has type 'unsigned int' [-Wformat]
common/cmd_nvedit.c: In function 'do_env_import':
common/cmd_nvedit.c:1047:3: warning: format '%zu' expects argument of
type 'size_t', but argument 2 has type 'unsigned int' [-Wformat]
common/cmd_nvedit.c:1047:3: warning: format '%zX' expects argument of
type 'size_t', but argument 3 has type 'unsigned int' [-Wformat]
lib/hashtable.c: In function 'hexport_r':
lib/hashtable.c:605:2: warning: format '%zu' expects argument of type
'size_t', but argument 5 has type 'unsigned int' [-Wformat]
lib/hashtable.c:661:5: warning: format '%zu' expects argument of type
'size_t', but argument 2 has type 'unsigned int' [-Wformat]
lib/hashtable.c:661:5: warning: format '%zu' expects argument of type
'size_t', but argument 3 has type 'unsigned int' [-Wformat]
lib/hashtable.c: In function 'himport_r':
lib/hashtable.c:793:3: warning: format '%zu' expects argument of type
'size_t', but argument 2 has type 'unsigned int' [-Wformat]
As you probably read from the list, Alison Wang and me are going to be
m68k custodians together, so i am starting reading all m68k things
that are open.
Best Regards,
Angelo Dureghello
next prev parent reply other threads:[~2014-12-02 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 20:41 [U-Boot] m68k: Build problems on some boards Angelo Dureghello
2014-12-01 23:17 ` Angelo Dureghello
2014-12-02 4:26 ` Masahiro Yamada
2014-12-02 9:22 ` Angelo Dureghello [this message]
2014-12-15 16:46 ` Masahiro YAMADA
2014-12-22 18:06 ` Angelo Dureghello
2015-01-26 20:54 ` Angelo Dureghello
-- strict thread matches above, loose matches on Subject: below --
2014-06-15 12:57 Vasili Galka
2014-06-22 9:19 ` Vasili Galka
2014-06-23 13:10 ` Tom Rini
2014-07-22 3:38 ` Masahiro Yamada
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=547D84E8.90900@sysam.it \
--to=angelo@sysam.it \
--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