From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Mon, 4 Feb 2013 09:49:12 +0100 Subject: [U-Boot] U-Boot Bug with newer GCC In-Reply-To: References: <20130201113111.DC53920055E@gemini.denx.de> <510CD045.8050207@denx.de> <510CE804.7020600@myspectrum.nl> <20130202123217.415914a7@lilith> <510D1D1E.7080705@myspectrum.nl> <20130202212217.467FA2000DF@gemini.denx.de> <510D88C7.7050201@myspectrum.nl> Message-ID: <20130204094912.4a799307@lilith> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Sebastian, On Mon, 4 Feb 2013 07:11:30 +0000, "Priebe, Sebastian" 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.