Adding Albert now...

On 2/3/12, Amit Virdi amitvi128@gmail.com wrote:

Albert,

Any suggestions?

Thanks Amit Virdi

On 2/1/12, Amit Virdi amitvi128@gmail.com wrote:

...

Hi All,

I'm in the process of updating platform support for spear series of SoC on the latest u-boot. I picked u-boot v2011.12. I tried compiling for different spear boards (spear 300, 310, 300 and spear600). In every compilation, I'm getting following errors:

---

arm-linux-ld: section .bss [007263cc -> 00728c5b] overlaps section .rel.dyn [007263cc -> 0072a623] arm-linux-ld: u-boot: section .bss lma 0x7263cc overlaps previous sections make: *** [u-boot] Error 1

---

This is one case.

Now if I apply some patches -all of them are either enhancing the features or are bug fixes - over the base line code, my code compiles *after* certain patch. None of these patches is changing any linker script.

I drilled down to the last patch that made the code compile without error. Specifically, that commit is configuring Network support for SPEAr SoCs.

Anyways, I did try to compare the map files generated for the good and the bad case but really couldn't conclude much!!

Any pointers?

Thanks Amit Virdi

On Fri, Feb 3, 2012 at 10:24 AM, Albert ARIBAUD albert.u.boot@aribaud.net wrote:

...

...

On 2/1/12, Amit Virdiamitvi128@gmail.com  wrote:

...

I'm in the process of updating platform support for spear series of SoC on the latest u-boot. I picked u-boot v2011.12. I tried compiling for different spear boards (spear 300, 310, 300 and spear600). In every compilation, I'm getting following errors:

---

arm-linux-ld: section .bss [007263cc ->  00728c5b] overlaps section .rel.dyn [007263cc ->  0072a623] arm-linux-ld: u-boot: section .bss lma 0x7263cc overlaps previous sections make: *** [u-boot] Error 1

---

This is one case.

In fact, .bss overlapping .rel.dyn is normal -- the linker file even explicitly states this with ".bss __rel_dyn_start (OVERLAY)".

Ok.

Which compiler do you use and which board exactly are you building?

As mentioned in the beginning of this mail, he tried compiling lot of boards, spear 300, 310, 300 and spear600.

There is a internal distribution from ST we are using, STLinux. Maybe we can try some other distribution, maybe Linaro. I can't really comment if this issue is due to the distributions we are using. :(

The latest by which Amit can try compiling it again is Monday. Lets see what other distribution gives.

-- viresh

Hi Amit,

Le 05/02/2012 12:29, Amit Virdi a écrit :

Albert,

On Sat, Feb 4, 2012 at 8:35 AM, viresh kumarviresh.linux@gmail.com wrote:

...

On Fri, Feb 3, 2012 at 10:24 AM, Albert ARIBAUD albert.u.boot@aribaud.net wrote:

...

...

...

On 2/1/12, Amit Virdiamitvi128@gmail.com wrote:

...

I'm in the process of updating platform support for spear series of SoC on the latest u-boot. I picked u-boot v2011.12. I tried compiling for different spear boards (spear 300, 310, 300 and spear600). In every compilation, I'm getting following errors:

---

arm-linux-ld: section .bss [007263cc -> 00728c5b] overlaps section .rel.dyn [007263cc -> 0072a623] arm-linux-ld: u-boot: section .bss lma 0x7263cc overlaps previous sections make: *** [u-boot] Error 1

---

This is one case.

In fact, .bss overlapping .rel.dyn is normal -- the linker file even explicitly states this with ".bss __rel_dyn_start (OVERLAY)".

Ok.

...

Which compiler do you use and which board exactly are you building?

We are using internal STLinux distribution. I tried compiling for spear320, and I couldn't succeed. Just to move a step further, can you please try "make spear320" at your end? If the error is not received at your end, I can be sure that the problem is due to the distribution at my end.

Thanks in advance.

Regards Amit Virdi

PS: I used v2011.12. "spear320" entry isn't there in the boards.cfg file. I shall be sending patch to update the same once I resolve this linking error.

Sorry, I should have stated this in the first place: I didn't see any warning with ELDK4.2 or with Linaro toolchain available in Ubuntu.

I just tried some CodeSource toolchains, and the 2009q1 emits the same error whereas the 2010q1 and 2011q1 don't.

Definitely a toolchain setting somewhere, and one that has disappeared in CS two years ago.

Amicalement,