SOLVED: Warning: "crtbegin.o" not found, this will probably ca

[PJW]

I've been using Lazarus and FPC on and off for a number of years on Windows, but I'm finally venturing into the Linux world.   I need to develop an small console app that will run on a Raspberry Pi.

I've got Lazarus 2.0.0 and FPC 3.0.4 installed (32 bit).  For some reason the newer versions do not seem to be available, but this version should be new enough for what I'm doing.

I'm getting the following Warning messages when compiling my app:

Warning: "crtbegin.o" not found, this will probably cause a linking failure
Warning: "crtend.o" not found, this will probably cause a linking failure

The program compiles and appears to be running properly, but I can't help but want to resolve these compiler warnings.   I searched for and found the two files, and added the following to my fpc.cfg file:

-Fl/usr/lib/gcc/arm-linux-gnueabihf/8

However this seems to break Lazarus/FPC.  When I start Lazarus, it complains it can't find the the compiler (FPC), so I assume I broke it by adding that line.   If I remove the line it works fine.

So I guess there are two questions:

1.  What did I do wrong and what do I need to do to fix it?
2.  What do these files do and what are the consequences of not linking them?

[marcov]

You probably miss some core package needed for development. Depending on distro it is called "build-essentials" or "glibc-dev"  or "glibc-devel".

[munair]

This is a GCC version problem.

First you need to find the version of GCC. You can do this by typing in the console/terminal:

gcc --version

On my Manjaro Linux this is currently 11.1.0.

Now check the version in /etc/fpc.cfg (you have to open the file as root/sudo). Scroll down until you see '# path to gcclib'. There you will find the GCC version that the compiler tries to find on your system:

Code: [Select]

# path to the gcclib
#ifdef cpui386
-Fl/usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/32
#endif
#ifdef cpux86_64
-Fl/usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0
#endif

As you can see, my FPC installation says 10.2.0 and as a result I get the same compiler warning. Adjust it to your GCC version (both lines):

Code: [Select]

# path to the gcclib
#ifdef cpui386
-Fl/usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/32
#endif
#ifdef cpux86_64
-Fl/usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0
#endif

In my case I changed it to 11.1.0 but it may be different on your system. Save the file and the problem is solved. If your GCC or FPC gets an update you may need to set the new version again in fpc.cfg.

[PJW]

Got it fixed!

I had the right object files all along, but was updating the wrong fpc.cfg.   I updated the correct one and now things worked.   I have no idea why updating the wrong one broke things though!

[munair]

Got it fixed!

I had the right object files all along, but was updating the wrong fpc.cfg.   I updated the correct one and now things worked.   I have no idea why updating the wrong one broke things though!

I only have one fpc.cfg file on my system, not sure which one you edited (unless you have more than one FPC version installed, if that is possible).

Anyway, if your problem is solved you might want to put that in the title. 

[Gustavo 'Gus' Carreno]

Hey Munair,

... (unless you have more than one FPC version installed, if that is possible).

It's very possible to have many installs of Lazarus/FPC.
I, myself, have 4 installs of different combinations of Lazarus and FPC installed under their own, self-contained folders all installed via fpcudeluxe.

When you install via the proper channels, either your OS repository(Linux) or via the packages on SourceForge, then you have a single install, system wide and it's a bit tricky to do parallel installs.

So in conclusion, it is possible to have multiple installs with different combinations of Lazarus/FPC, but you can't use the methods of the proper channels, you either do it by hand or use a tool like fpcupdeluxe.

Cheers,
Gus

[winni]

Hi!

I had the same error.

I am not quit shure  but I think it happened  when I did an update to fpc 3,2 via the Suse repository.

Grrr! And every Linux  distro has it's own path.

For Suse it is:

Code: Bash  [Select][+][-]

1. /usr/lib64/gcc/x86_64-suse-linux/11

Winni

[munair]

When you install via the proper channels, either your OS repository(Linux) or via the packages on SourceForge, then you have a single install, system wide and it's a bit tricky to do parallel installs.

Yes, I was referring to Linux, as the OP did. With parallel installs it is a matter of finding the right fpc.cfg files, but I have not much experience with that.

[munair]

I am not quit shure  but I think it happened  when I did an update to fpc 3,2 via the Suse repository.

Yeah, it's a bit annoying. Ideally, Lazarus should automatically detect the GCC version and adjust/warn if it has changed or expects a different version. Particularly for new comers who are familiarizing themselves with FPC/Lazarus, this is intimidating because they get the false sense that they've done something wrong whereas in truth they didn't. As far as I remember this has been a problem and while not fatal, it deserves a fix IMHO.

[winni]

Hi!

Yes - everything compiled fine.
But I always had the anoying message with crtbegin.o and crtend.o

As this was new to me I wanted to know the reason.

Winni

[Awesome Programmer]

Even though this is an old post, the answers provided still works today.

My hardrive recently crashed on my linux system. So, I had to reinstall and rebuild my linux system not mention all the upgrades. That broke a lot of my setup and one of them was this annoying error about crtbeginS.o not found.

This fixed it.
Thank you.

[Thaddy]

Yes, it simply needs a correct install of the GNU C suite and the correct path to its libs.
You can also fix it manually.

[daniel_sap]

I have the same warning messages when compiling under ubuntu.
Can I just leave them like that and do not provide any paths, cause the compilation is successfull and the compiled binary works fine.
Or may be there will be some negative effect which I don't notice at the moment

[Thaddy]

They are only needed when you do a lot of interfacing with C libraries:
crt means c runtime libraries.
But it is still a good idea to resolve it and include the current C libraries in your path.
it merely initializes and finalizes the c runtime stuff.
The "problem" is just windows related if there are no clibs in the path.
On linux it won't occur afaik.

[cdbc]

Hi
@Thaddy: Nah, got a new quote, have we?!? 
I'd have thought, The Toy Boys were censured listening, but you're right nifty little song THIS.
Thanks mate, for the blast from the past... 
Regards Benny