crtbeginS.o and crtendS.o not found this will probably cause a linking failure lazarus / 21-General ---------------------------------------------------------------------- Aruna · 2025-05-18 14:48 Hello everyone, I just installed Lazarus IDE onto a fresh clean pristine installation of Debian Linux and tried to compile a empty project just to make sure everything works as expected. Everything does work but I get two error messages. Screenshot attached shows the errors. How do I make them go away? ---------------------------------------------------------------------- paule32 · 2025-05-18 15:11 I faced this by using the gcc.exe - the gnu proxy to cc.exe when the path's not set (maybe on -nostdlib, too). Check, if you use a clean/valid fpc.ini. ---------------------------------------------------------------------- munair · 2025-05-18 15:25 This is a GCC version problem in fpc.cfg. Solution: https://forum.lazarus.freepascal.org/index.php/topic,56114.msg417087.h tml#msg417087 ---------------------------------------------------------------------- TRon · 2025-05-18 15:27 Quote from: Aruna on May 18, 2025, 04:48:55 pmEverything does work but I get two error messages. Screenshot attached shows the errors. How do I make them go away? In the fpc.cfg used by the compiler is an entry that looks something like: Code: [Select]# path to the gcclib #ifdef cpui386 -Fl/usr/lib/gcc/x86_64-linux-gnu/12 #endif #ifdef cpux86_64 -Fl/usr/lib/gcc/x86_64-linux-gnu/12 #endif Note the number at the end. This number as well as the location of the gcc dependencies might be located in another directory on your system. I am not that familiar with gcc to know if there is a default way to determine the exact location (there probably is one). If not mistaken then usually package build-essential (debian based distros at least) takes care of retrieving these dependencies. ---------------------------------------------------------------------- Lutz Mändle · 2025-05-18 15:55 The command gcc --print-libgcc-file-name prints the path for the actual gcc installation. On opensuse tumbleweed (64 bit) it gives: /usr/lib64/gcc/x86_64-suse-linux/14/libgcc.a The -Fl option in the fpc.cfg needs only the path without libgcc.a . ---------------------------------------------------------------------- TRon · 2025-05-18 16:01 * TRon tips hat to Lutz ---------------------------------------------------------------------- Aruna · 2025-05-18 21:38 Hi, @munair @Tron and @Lutz thank you so much everyone. Strangely in my /etc/fpc.cfg the # path to the gcclib was empty. So I plugged this in and the warnings went away: Code: Text  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i #ifdef cpui386-Fl/usr/lib/gcc/x86_64-linux-gnu/12#endif#ifdef cpux86_64-Fl/usr/lib/gcc/x86_64-linux-gnu/12#endif Once again many thanks to all for the guidance and help. ---------------------------------------------------------------------- munair · 2025-05-19 20:18 You're welcome. Whenever your GCC gets updated, be sure to adjust the version number in fpc.cfg. ---------------------------------------------------------------------- cdbc · 2025-05-20 08:00 Hi @Munair: +1 =^ Regards Benny ---------------------------------------------------------------------- PeterBB · 2025-05-20 10:29 Quote from: munair on May 19, 2025, 10:18:46 pmWhenever your GCC gets updated, be sure to adjust the version number in fpc.cfg. And there is a tool, fpcmkcfg. that can do this for you. Cheers, Peter ---------------------------------------------------------------------- arnoldpa · 2025-05-28 09:09 Quote And there is a tool, fpcmkcfg. that can do this for you. Cheers, Peter I've been having the same warning also. Thanks for the tip.