Hello, > (maybe you should set your mailing tool to wrap at ~70 characters)
Apperently I can't. The mailing tool (MS Outlook) setting are restricted by my companys IT. I have no "root" rights on my windows machine. I develop only on my linux machine. > If there is no linker_list.h, then the patch is basically not applicable -- > you'd have to hand-port it by manually rewriting the linker file to include > sections instead of defining symbols, something like I will wait until we upgraded to v2013.01 and apply the patch then. The problem seems to be solved, as several mailings said. I will work with the old toolchain until our upgrade. If the problem still exists after the upgrade I will scream again ;-) Thanks for the fast support. 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:[email protected]] Gesendet: Montag, 4. Februar 2013 15:32 An: Priebe, Sebastian Cc: Jeroen Hofstee; Wolfgang Denk; Marek Vasut; [email protected]; Heiko Schocher Betreff: Re: [U-Boot] U-Boot Bug with newer GCC Hi Sebastian, On Mon, 4 Feb 2013 14:23:17 +0000, "Priebe, Sebastian" <[email protected]> wrote: > Hello, > > > Do you mean the only change you see at all is this new line addition? I > > suspect there are other changes, which you missed, maybe because they apply > > fine. What does a 'git status' produce? > > We are using svn, not git. There are too many differences. I can't apply the > patch. There is no e.g. linker_list.h, etc... > svn status after patching show only command/command.c changed. (maybe you should set your mailing tool to wrap at ~70 characters) If there is no linker_list.h, then the patch is basically not applicable -- you'd have to hand-port it by manually rewriting the linker file to include sections instead of defining symbols, something like .u_boot_cmd_start : { KEEP(*(.u_boot_cmd_start)) } .u_boot_cmd : { KEEP(*(.u_boot_cmd)) } .u_boot_cmd_end : { KEEP(*(.u_boot_cmd_end)) } And then, somewhere in a C file, define __u_boot_cmd_start as a 'struct {}' placed in section .u_boot_cmd_start, and __u_boot_cmd_end as a struct {} placed in section .u_boot_cmd_end. > Greetings, > Sebastian Amicalement, -- Albert. _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
