GCC: Linker (Script) error?
Posted: Wed Aug 27, 2014 8:06 am
This is what i get when i compile programs (ports or amiga programs, doesn't matter) on the serial console
Nothing on the serial though, no crash log, no crash indication, it just froze solid (This makes me think it is a hardware problem?)
My question now...is this an indication to gcc/g++ having a problem?
Is this behaviour known and being worked on/on the todo list?
Is it maybe some setting i need to change and if so, which setting?
Thanks for all the hints
While it normally doesn't do any harm, i switched on the serial console to see why i kept getting system freezes randomly when doing something performance-hungry in the background...like surfing the web with Odyssey.[elf] .hash 0x7FCEC000-0x7FCEC4CC System:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .dynsym 0x7FCEC4CC-0x7FCECFAC System:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .dynstr 0x7FCECFAC-0x7FCED78A System:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.data 0x7FCED78C-0x7FCED7A4 System:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.dyn 0x7FCED7A4-0x7FCEDB1C System:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.plt 0x7FCEDB1C-0x7FCEDC9C System:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
Nothing on the serial though, no crash log, no crash indication, it just froze solid (This makes me think it is a hardware problem?)
My question now...is this an indication to gcc/g++ having a problem?
Is this behaviour known and being worked on/on the todo list?
Is it maybe some setting i need to change and if so, which setting?
Thanks for all the hints