In winding my way through various checks and test of RTEMS 5, I tried linking some of my executables with '-Wl,--orphan-handling=error'. I've been bitten in the past by the (imo. unfortunate) default behavior in combination with an incomplete linker script, so this is on my list of things to try.
The generated pc686 executables seem to boot and run correctly in QEMU. >From the link map ("-Wl,-Map,...") these sections are all empty, so the default wherever placement rules don't break anything. I'm not sure if there are circumstances where this would not be the case for a static executable. > error: unplaced orphan section `.iplt' from > `/home/travis/.rtems/5/i386-rtems5/pc686/lib//start.o' > error: unplaced orphan section `.rel.iplt' from > `/home/travis/.rtems/5/i386-rtems5/pc686/lib//start.o' > error: unplaced orphan section `.igot.plt' from > `/home/travis/.rtems/5/i386-rtems5/pc686/lib//start.o' > error: unplaced orphan section `.rel.gcc_except_table.main' from > `/home/travis/.rtems/5/i386-rtems5/pc686/lib//start.o' There are some other '.rel.gcc_except_table.*' coming from my code. > error: unplaced orphan section > `.rel.rtemsroset._Sysinit.content.0.0x00030080' from > `/home/travis/.rtems/5/i386-rtems5/pc686/lib//start.o' > error: unplaced orphan section `.tm_clone_table' from > `/home/travis/.rtems/5/lib/gcc/i386-rtems5/7.5.0/mpentium/crtbegin.o' > error: unplaced orphan section `.tm_clone_table' from > `/home/travis/.rtems/5/lib/gcc/i386-rtems5/7.5.0/mpentium/crtend.o _______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users