Hello fredvs, Sie schrieben am Sun, 22 Jul 2018 16:06:13 -0500 (CDT):
> 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 It seems normal - > 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. - considering, that these two _object_ files seem to be multi architacture in systems with multi architecture support. > So IMHO it is a sytem problem (or is it fpc that does the search+test ELF > ?). You're _certain_ that these files are really multi-arch and were not replaced by single-arch files by a previous update? BTW, on my system, the lib32-versions of crti.o and crtn.o evidently are _not_ multi-arch, but 32bit only. But I must admit that I do not know whether fpc uses the system linker "ld" (which I used to find the above mentioned things) or has one integrated into itself. -- -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- ------------------------------------------------------------------------------ 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
