[PATCH] Lejos OSEK 1.07 to 1.09: don't discard init.o Options

[AlexN]

Hi,

I found the reason for my linking problem under Linux, init.o was discarded/ignored starting with version 1.07. This caused that main() wasn't called and so nothing at all was called so everything was discarded,

The linker script changed like this from 1.06 to 1.07:

- init.o (*.text *.text.*)
+ */init.o (*.text *.text.*)

since init.o was now in some subdirectory. But apparently using */init.o also means something like "don't complain if you can't find the file", I could branch to whatever non-existing functions I like, I never got unresolved symbols, i.e. the file was ignored completely.
I fixed this by using the full path to the init.o (sed is required for that) and by putting it inside a KEEP() instruction.

The attached patch is against 1.09 and makes it work under Linux again, please apply.

Alex

Attached File(s)

 keep_init_o.patch.txt ( 1.91k ) Number of downloads: 6

 

[takashic]

Hi,

I found the reason for my linking problem under Linux, init.o was discarded/ignored starting with version 1.07. This caused that main() wasn't called and so nothing at all was called so everything was discarded,

The linker script changed like this from 1.06 to 1.07:

- init.o (*.text *.text.*)
+ */init.o (*.text *.text.*)

since init.o was now in some subdirectory. But apparently using */init.o also means something like "don't complain if you can't find the file", I could branch to whatever non-existing functions I like, I never got unresolved symbols, i.e. the file was ignored completely.
I fixed this by using the full path to the init.o (sed is required for that) and by putting it inside a KEEP() instruction.

The attached patch is against 1.09 and makes it work under Linux again, please apply.

Alex

Hi Alex,

Thank you very much!
I will apply your patch to the next release and add some description for Linux users.

Takashi