> -Original Message-
> From: u-boot-boun...@lists.denx.de
> [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Dirk Behme
> Sent: Friday, December 17, 2010 4:10 PM
> To: Wolfgang Denk
> Cc: u-boot@lists.denx.de
> Subject: Re: [U-Boot] OMAP3: EVM: Linker errors
On 16.12.2010 11:10, Dirk Behme wrote:
> On 14.12.2010 17:21, Wolfgang Denk wrote:
>> Dear Dirk,
>>
>> In message<4d079060.70...@googlemail.com> you wrote:
>>>
>>> I did a readelf analysis for 3 test cases (with 2009q1-203):
>>
>> Which exact versions of GCC and binutils is this?
>
> gcc version 4.
Am 16.12.2010 16:20, schrieb Dirk Behme:
> On 16.12.2010 14:47, Alexander Holler wrote:
>> I'm working with the master (f8689b9eb3a7f6925cd50404a12479889188c510)
>> on a beagleboard
> ^^
>
> ?
>
> This thread is about a (linking) issue building 'omap3_evm'.
>
> The Beagle su
On 16.12.2010 14:47, Alexander Holler wrote:
> Am 14.12.2010 17:01, schrieb Albert ARIBAUD:
>> Le 14/12/2010 16:42, Dirk Behme a écrit :
>>
>> (agree about the analysis)
>>
>>> So I'd like to re-send the int conversion patch from
>>>
>>> http://lists.denx.de/pipermail/u-boot/2010-December/083524.ht
Am 16.12.2010 14:47, schrieb Alexander Holler:
> To put some salt into the wounds ;) , Using gcc 4.5.1 board_init_f isn't
> reached here. When I'm using gcc 4.3.5 it is reached. In both cases I've
> used the same version of binutils, 2.20.1.
>
> For a test without using jtag, I've modified board_i
Am 14.12.2010 17:01, schrieb Albert ARIBAUD:
> Le 14/12/2010 16:42, Dirk Behme a écrit :
>
> (agree about the analysis)
>
>> So I'd like to re-send the int conversion patch from
>>
>> http://lists.denx.de/pipermail/u-boot/2010-December/083524.html
>>
>> in a proper format again as a workaround for
On 14.12.2010 17:21, Wolfgang Denk wrote:
> Dear Dirk,
>
> In message<4d079060.70...@googlemail.com> you wrote:
>>
>> I did a readelf analysis for 3 test cases (with 2009q1-203):
>
> Which exact versions of GCC and binutils is this?
gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203). For binutils
Dear Dirk,
In message <4d079060.70...@googlemail.com> you wrote:
>
> I did a readelf analysis for 3 test cases (with 2009q1-203):
Which exact versions of GCC and binutils is this?
Do we see any differences in board/ti/evm/evm.o ?
Can just use a different linker?
Or use a different tool chain f
Dear Albert ARIBAUD,
In message <4d0794cf.5090...@free.fr> you wrote:
>
> I think Wolfgang does not want this fix if it is a workaround to a bug,
> although it is not clear to me if this includes toolchain bugs. In any
> case, the decision will be Wolfgang's, so it's best if he's Cc:ed just
>
On 12.12.2010 12:40, Albert ARIBAUD wrote:
> Le 12/12/2010 11:32, Dirk Behme a écrit :
>
> >> 2. IIRC, the linker emits a warning, not an error. We can live some
> >> time with a warning if it is documented and it is being worked on.
> >
> > With 2009q1-203 it's an error and 'omap3_evm' isn't b
Le 14/12/2010 16:42, Dirk Behme a écrit :
(agree about the analysis)
> So I'd like to re-send the int conversion patch from
>
> http://lists.denx.de/pipermail/u-boot/2010-December/083524.html
>
> in a proper format again as a workaround for this issue.
>
> Ok?
I think Wolfgang does not want this
Le 12/12/2010 11:32, Dirk Behme a écrit :
>> 2. IIRC, the linker emits a warning, not an error. We can live some
>> time with a warning if it is documented and it is being worked on.
>
> With 2009q1-203 it's an error and 'omap3_evm' isn't built:
>
> arm-none-linux-gnueabi-ld: section .bss [
On 12.12.2010 11:08, Albert ARIBAUD wrote:
> Hi Dirk,
>
> Le 12/12/2010 09:25, Dirk Behme a écrit :
>>
>> What's the status of the linker errors across tool chain versions seen
>> by building the 'omap3_evm' board?
>>
>> This was already discussed in the threads [1] and [2], but it seems to
>> me t
Hi Dirk,
Le 12/12/2010 09:25, Dirk Behme a écrit :
>
> What's the status of the linker errors across tool chain versions seen
> by building the 'omap3_evm' board?
>
> This was already discussed in the threads [1] and [2], but it seems to
> me that there was no acceptable fix, yet?
>
> E.g. with Co
What's the status of the linker errors across tool chain versions seen
by building the 'omap3_evm' board?
This was already discussed in the threads [1] and [2], but it seems to
me that there was no acceptable fix, yet?
E.g. with CodeSourcery's tool chain 2009q1-203 I get
arm-none-linux-gnueab
15 matches
Mail list logo