On Sunday 22 July 2018 23:06:13 fredvs wrote: > Re-hello. > > Here a advice that has absolutely no importance. > > OK, -Xd does the trick because it does not give /lib nor /usr/lib as searh > path. > > But I maintain that there is still a problem with crti.o and crtn.o > > It is not normal that all other needed libraries are using the correct 32 > bit path (/usr/lib32) and not crti.o and crtn.o > > Normally, like for all other libraries, the system try to find in each > search path (begining with the first in list) the needed library with the > correct ELF 32 bit. > > If the system find one that is ELF 64, it will try a other search path > until it discover a good ELF 32 bit. > > 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.
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 [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
