On Wednesday 25 July 2018 21:58:25 fredvs wrote: > > About the ctri.o and ctrn.o problems, the -Xd parameter fixes the linking > (but I did not find why the 64 bit object-files are assigned in place of 32 > bit). > Because in linker script are absolute paths, see my mail from 2018-07-23:
" > > But is seems that for crti.o and crtn.o if they are ELF 64, there are > > recognized as ELF 32. > > In INPUT statement there are absolute paths for crtend.o and crtn.o. > " > /usr/lib32/crtend.o > /lib/crtn.o <<<--- wrong > " > and > " > /usr/lib32/crtend.o > /usr/lib32/crtn.o > " > I don't know how FPC decides which one of the found modules to use so it is > better to add -Xd. " I assume the reason must be searched in FPC code. Martin ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
