Hello,
Did you try to 'apply --reject' the patch to 2012.10 and see how this goes?
This only adds a newline in command.c.
Regards, Sebastian
========================================== CADCON Ingenieurgesellschaft mbH & Co. KG Geschaeftsfuehrer: Robert Bauer, Andreas Gundel Sitz der Gesellschaft: D-86368 Gersthofen Registergericht: Amtsgericht Augsburg HRA 14521 ========================================== -----Ursprüngliche Nachricht----- Von: Albert ARIBAUD [mailto:albert.u.boot@aribaud.net] Gesendet: Montag, 4. Februar 2013 09:49 An: Priebe, Sebastian Cc: Jeroen Hofstee; Wolfgang Denk; Marek Vasut; u-boot@lists.denx.de; Heiko Schocher Betreff: Re: [U-Boot] U-Boot Bug with newer GCC
Hi Sebastian,
On Mon, 4 Feb 2013 07:11:30 +0000, "Priebe, Sebastian" Sebastian.Priebe@cadcon.de wrote:
Hello,
So it seems to be, that patch at least solves this issue. Sebastian: can you check if this is resolved also resolved for your board after applying http://patchwork.ozlabs.org/patch/217695/
Apperently we are still working with v2012.10. Could someone be so kind and provide a patch for v2012.10? We plan to upgrade to v2013.01, but not before the end of Februay.
Did you try to 'apply --reject' the patch to 2012.10 and see how this goes?
Then this smells like a tool chain issue. You might contact Pengutronix support for help with their tool chain.
We already asked Pengutronix. They use barebox with their toolchains and didn't have any problem with their new toolchain, yet. In their barebox.lds they have: __barebox_cmd_start = .; __barebox_cmd : { KEEP(*(SORT_BY_NAME(.barebox_cmd*))) } __barebox_cmd_end = .;
And they thought __u_boot_cmd_start = .; .u_boot_cmd : { KEEP(*(.u_boot_cmd)) } __u_boot_cmd_end = .;
would solve the problem. But it didn't.
As long as symbols are defined at linker level it won't, I guess. My patch actively changes the way the commands start and end symbols are defined.
Best regards. Sebastian
Amicalement, -- Albert.