SOLVED: Warning: "crtbegin.o" not found, this will probably ca
lazarus / 32-Linux

----------------------------------------------------------------------
PJW · 2021-09-02 21:42

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 · 2021-09-02 22:09

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

----------------------------------------------------------------------
munair · 2021-09-02 23:14

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 · 2021-09-02 23:25

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 · 2021-09-03 06:06

Quote from: PJW on September 03, 2021, 01:25:15 amGot 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 · 2021-09-03 19:45

Hey Munair,

Quote from: munair on September 03, 2021, 08:06:42 am... (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 · 2021-09-03 20:40

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][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i
/usr/lib64/gcc/x86_64-suse-linux/11
Winni

----------------------------------------------------------------------
munair · 2021-09-03 21:05

Quote from: Gustavo 'Gus' Carreno on September 03, 2021, 09:45:25
pmWhen 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 · 2021-09-03 21:15

Quote from: winni on September 03, 2021, 10:40:25 pmI 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 · 2021-09-03 21:28

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 · 2025-04-29 16:01

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 · 2025-04-29 16:43

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 · 2025-05-05 19:37

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 · 2025-05-06 08:32

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 · 2025-05-06 09:49

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

----------------------------------------------------------------------
Thaddy · 2025-05-06 12:09

@cdbc
Yes, that's it   Great fan for many years, Have most of their old
records...
First met them when I was at my student society. They were playing at
us and I had to may them 6500 guilders back in the eighties. (Questor
Societeit)
They blew the roof off. Yhey are apparently from Durroemm, what ever
that means. (Maybe Durham?) Incompehenceble dialect. Nice tele,
though, I played it! (Since Nelly is a girl, I hope I did not offend
the lhgbt community)

Off to the circus with that one. Btw It is a much older English child
song, but you knew that.

----------------------------------------------------------------------
TRon · 2025-05-06 17:40

Quote from: Thaddy on May 06, 2025, 10:32:54 amOn linux it won't occur
afaik.
fyi it can and will. Nothing a little nudge is able to solve though.

----------------------------------------------------------------------
munair · 2025-05-10 07:18

Quote from: Thaddy on May 06, 2025, 10:32:54 amThe "problem" is just
windows related if there are no clibs in the path.
On linux it won't occur afaik.
The topic started out with the problem and fix on Linux.

----------------------------------------------------------------------
Thaddy · 2025-05-10 09:07

Then he had no correct install anyway.

----------------------------------------------------------------------
lazer · 2025-09-01 11:22

I'm having the crtbegin.o issue too.

It's been a while but I had laz and fpc working nicely on fedora 40. 
Since I've just updated to Fed42 and wanted to pick up some laz
project I had worked on before.

Of course, some things don't work any more
My project compiles but uos sound library does not load. In digging
into this I noticed crtbegin warning.

My /etc/fpc,cfg looks a little different to some posted above in that
it does not have hardcoded version numbers (thankfully).

Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i #
searchpath for libraries#IFDEF CPU64#-
Fl/usr/lib64/fpc/$fpcversion/lib#-Fl/lib64;/usr/lib64-
Fl/usr/lib64/fpc/$fpcversion/lib/$FPCTARGET#ELSE#-
Fl/usr/lib/fpc/$fpcversion/lib#-Fl/lib;/usr/lib-
Fl/usr/lib/fpc/$fpcversion/lib/$FPCTARGET#ENDIF # searchpath for
tools#IFDEF CPU64-FD/usr/lib64/fpc/$fpcversion/bin/$FPCTARGET#ELSE-
FD/usr/lib/fpc/$fpcversion/bin/$FPCTARGET#ENDIF 
Now, using distro's fpc
Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i $ fpc
-vFree Pascal Compiler version 3.2.2 [2025/05/10] for x86_64 
I do find /usr/lib64/fpc/$fpcversion/  but there is no lib or bin.

Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i $ ls
/usr/lib64/fpc/3.2.2fpmkinst  msg  ppcx64  samplecfg  units 
I don't know where lib and bin went  but lazarus seems to build and
run my program without any problem except for the missing sound.

this is where it is failing:
Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i  //function
uos_loadlib(PortAudioFileName, SndFileFileName, Mpg123FileName,
Mp4ffFileName, FaadFileName,  opusfilefilename: PChar) : LongInt; 
res:=0;  res := uos_LoadLib(PChar(PA_FileName), PChar(SF_FileName),
nil, Nil, Nil, Nil);   if res <> 0 then    errdisp('sound libraries
did not load.',strNotxt,mb_excl)   // add to translated strings in
pack.pas ???  else  begin 
Is that related to the crtbegin.o warning or am I running around in
circles here?

TIA.

----------------------------------------------------------------------
Thaddy · 2025-09-01 11:46

Add -Fl/usr/lib/gcc/x86_64-linux-gnu/13 (on my machine)

----------------------------------------------------------------------
Lutz Mändle · 2025-09-01 12:00

The path for the -Fl option in fpc.cfg can requested from gcc with the
command
gcc --print-libgcc-file-name

On actual opensuse Tumbleweed it gives
/usr/lib64/gcc/x86_64-suse-linux/15/libgcc.a

From this answer copy only the directory part to the -Fl option.

----------------------------------------------------------------------
lazer · 2025-09-01 15:07

Thanks folks.  That seems to have fixed the crtbegin.o  issue.

Sadly still no sound.  Looks like I'm in for a day's worth of
debugging to straighten that out.

----------------------------------------------------------------------
Thaddy · 2025-09-01 15:20

Quote from: Lutz Mändle on September 01, 2025, 02:00:32 pmgcc --print-
libgcc-file-name
Indeed, great to find the path part.
That's a neat trick I did not know. And it works on multiple
debians/ubuntu too.
Should be in the wiki...

----------------------------------------------------------------------
cdbc · 2025-09-01 15:23

Hi
QuoteThat's a neat trick I did not know. And it works on multiple
debians/ubuntu too.
Should be in the wiki...+1
Works on PCLinuxOS too -- Me Likey 
Yup, somebody please put it in the wiki...
Regards Benny

----------------------------------------------------------------------
lazer · 2025-09-02 07:24

Quote from: cdbc on September 01, 2025, 05:23:14 pmYup, somebody
please put it in the wiki...

How about someone puts in the fpc.cfg so we don't have to screw about
trawling forums ?

----------------------------------------------------------------------
Thausand · 2025-09-02 07:29

Quote from: lazer on September 02, 2025, 09:24:13 amHow about someone
puts in the fpc.cfg so we don't have to screw about trawling forums ?
fpc.cfg no can execute program so not work.

----------------------------------------------------------------------
Thaddy · 2025-09-02 07:43

Quote from: lazer on September 02, 2025, 09:24:13 amHow about someone
puts in the fpc.cfg so we don't have to screw about trawling forums ?
That is unlikely since it depends on the GNU version that is installed
on your system.
What is possible is that an installer writes that line based on the
tip given above.
Then again, i lived for years simply ignoring the crtbegin/end
messages on some systems.

----------------------------------------------------------------------
lazer · 2025-09-02 08:11

There does not seem to be any scripting in fpc.cfg but some variables
are apparently sniffed higher up and passed to it.
Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i #IFDEF
CPU64-Fu/usr/lib64/fpc/$fpcversion/units/$fpctarget-Fu/usr/lib64/fpc/$
fpcversion/units/$fpctarget/*-
Fu/usr/lib64/fpc/$fpcversion/units/$fpctarget/rtl 
Presumably it could do something like:
Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i #
searchpath for libraries#IFDEF CPU64#-
Fl/usr/lib64/fpc/$fpcversion/lib#-Fl/lib64;/usr/lib64-
Fl/usr/lib64/fpc/$fpcversion/lib/$FPCTARGET # find glibc path:  gcc
--print-libgcc-file-name-Fl/usr/lib/gcc/$gcctarget/$gccversion 
QuoteThen again, i lived for years simply ignoring the crtbegin/end
messages on some systems.Oh, so this is a total red herring anyway?

----------------------------------------------------------------------
Thausand · 2025-09-02 08:17

Quote from: lazer on September 02, 2025, 10:11:52 amPresumably it
could do something like:
Yes, can have. Envar can use in fpc.cfg. I do with fpc script make
them then have run fpc executable.

QuoteOh, so this is a total red herring anyway?
Not if work depend heavy on c when need crt function(s) or OS/platform
depend for it. So for "normal" work it no really matter afaik

----------------------------------------------------------------------
Thaddy · 2025-09-02 08:53

Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i {$mode
objfpc}{$H+}uses  sysutils, classes, process;var  gnupath:TProcess; 
cfg:TStringlist;begin  gnupath := TProcess.Create(nil); 
gnupath.Options := [poUsePipes,poWaitOnExit];  gnupath.executable :=
'gcc';  gnupath.parameters.add('--print-libgcc-file-name'); 
gnupath.execute;  cfg := TStringlist.Create; 
cfg.LoadFromStream(gnupath.Output); 
writeln('-Fl'+extractfilepath(cfg.text));// add to fpc.cfg if it is
not already there.  cfg.free;  gnupath.free;end.

----------------------------------------------------------------------
rvk · 2025-09-02 08:57

I have this in my automatic build script for trunk:

Code: Bash  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i # sudo find
/ -name crtbegin.o# This library needs to be added to the fpc.cfg
file. cat << EOF >> $HOME/.fpc.cfg-
Fu$BASE/fpc/lib/fpc/\$fpcversion/units/\$fpctarget-Fu$BASE/fpc/lib/fpc
/\$fpcversion/units/\$fpctarget/*-
Fu$BASE/fpc/lib/fpc/\$fpcversion/units/\$fpctarget/rtl-Fl$(dirname
$(gcc --print-file-name=crtbegin.o))-FD$BASE/fpc/binEOF
So with gcc --print-file-name=crtbegin.o you get the correct
directory.

(The parameter --print-libgcc-file-name Thaddy gave will probably be
pointing to the same directory in 99,9999% of the cases.)

----------------------------------------------------------------------
lazer · 2025-09-02 09:18

Cool stuff. 

I'm trying to get away from maintaining my own out of tree build of
FPC .
Can these mods be included in the official tree?

----------------------------------------------------------------------
Thaddy · 2025-09-02 10:24

@rvk
Don't forget to add crtend as well

----------------------------------------------------------------------
rvk · 2025-09-02 10:33

Quote from: Thaddy on September 02, 2025, 12:24:30 pm@rvk
Don't forget to add crtend as well
Haha, I assumed crtend.o is in the same directory as crtbegin.o — but
I guess that’s also 'only' true 99.9999% of the time

----------------------------------------------------------------------
PeterBB · 2025-09-03 20:02

On Linux systems with fpc installed there is usually a tool fpcmkcfg

It writes out a default config file to stdout. It will have the
current gcc versions in it.

Try
Code: [Select]man fpcmkcfg

----------------------------------------------------------------------
lazer · 2025-09-03 20:25

If I run that command here is part of the output:

Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i #
searchpath for tools-FD/bin/$FPCTARGET # path to the gcclib#ifdef
cpui386-Fl/usr/lib/gcc/x86_64-redhat-linux/15/32#endif#ifdef
cpux86_64-Fl/usr/lib/gcc/x86_64-redhat-linux/15#endif # searchpath for
libraries#-Fl/lib#-Fl/lib;/usr/lib-Fl/lib/$FPCTARGET 
cf
Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i gcc
--print-libgcc-file-name/usr/lib/gcc/x86_64-redhat-linux/15/libgcc.a 
However something seems to filter this out of my /etc/fpc.cfg.
Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i #
searchpath for fppkg user-specific packages-
Fu~/.fppkg/lib/fpc/$fpcversion/units/$FPCTARGET/* # path to the
gcclib  # searchpath for libraries#IFDEF CPU64#-
Fl/usr/lib64/fpc/$fpcversion/lib#-Fl/lib64;/usr/lib64-
Fl/usr/lib64/fpc/$fpcversion/lib/$FPCTARGET#ELSE#-
Fl/usr/lib/fpc/$fpcversion/lib#-Fl/lib;/usr/lib-
Fl/usr/lib/fpc/$fpcversion/lib/$FPCTARGET#ENDIF

----------------------------------------------------------------------
PeterBB · 2025-09-03 20:59

Quote from: lazer on September 02, 2025, 09:24:13 amHow about someone
puts in the fpc.cfg

The first few lines of my /etc/fpc.cfg are;

Code: [Select]#
# Config file generated by fpcmkcfg on 3-9-25 - 10:37:08
# Example fpc.cfg for Free Pascal Compiler
#

----------------------------------------------------------------------
lazer · 2025-09-03 21:12

Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i head
/etc/fpc.cfg## Config file generated by fpcmkcfg on 10-5-25 -
15:52:40# Example fpc.cfg for Free Pascal Compiler#  
This is old. I reinstalled fpc today. Maybe its been changed.

----------------------------------------------------------------------
PeterBB · 2025-09-03 21:13

Quote from: lazer on September 03, 2025, 10:25:05 pmHowever something
seems to filter this out of my /etc/fpc.cfg.
Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i #
searchpath for fppkg user-specific packages-
Fu~/.fppkg/lib/fpc/$fpcversion/units/$FPCTARGET/* # path to the
gcclib  # searchpath for libraries#IFDEF CPU64#-
Fl/usr/lib64/fpc/$fpcversion/lib#-Fl/lib64;/usr/lib64-
Fl/usr/lib64/fpc/$fpcversion/lib/$FPCTARGET#ELSE#-
Fl/usr/lib/fpc/$fpcversion/lib#-Fl/lib;/usr/lib-
Fl/usr/lib/fpc/$fpcversion/lib/$FPCTARGET#ENDIF 
I wonder if that would happen if fpc was installed before gcc?
Or if some gcc libraries were missing at the time?

----------------------------------------------------------------------
lazer · 2025-09-04 05:15

No gcc is one of the first things I install on a new system. Long
before thinking about fpc.

Also , I just removed distro fpc, renamed the old /etc/fpc.cfg and
reinstalled fpc

Old and new configs are identical. I also notice that the bin and lib
paths it sets do not exist , only units is populated.

Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i ls
/usr/lib64/fpc/*fpmkinst  msg  ppcx64  samplecfg  units

----------------------------------------------------------------------
Thaddy · 2025-09-04 07:36

rvk wrote explicitly that his code needs to be added to /etc/fpc.cfg

But note that if you installed through fpcupdeluxe a different fpc.cfg
may be used.

----------------------------------------------------------------------
rvk · 2025-09-04 07:56

Quote from: Thaddy on September 04, 2025, 09:36:34 amrvk wrote
explicitly that his code needs to be added to /etc/fpc.cfg
In my script it was needed (way back in 2018).

But looking back... it seems that now I have duplicate lines of the
gcc lib.
Code: Bash  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i # cat
./.fpc.cfg | grep 12-Fl/usr/lib/gcc/aarch64-linux-
gnu/12-Fl/usr/lib/gcc/aarch64-linux-gnu/12
I'm not sure if that's always been the case. Could it be that the
addition of "# path to the gcclib" by fpcmkcfg???

My script is from before 2018 and maybe fpcmkcfg wasn't adding then
yet.
I can remember adding this to my script because of the errors of
missing crtbegin.o and crtend.o.

Or could it be the ifdefs don't always trigger that line?
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 # path to
the gcclib#ifdef Linux#ifdef cpuaarch64-Fl/usr/lib/gcc/aarch64-linux-
gnu/12#endif#endif

----------------------------------------------------------------------
rvk · 2025-09-04 08:05

Ha, my script was even from before 2016. I see in very old
instructions I used to use samplecfg.
Maybe the samplecfg didn't add that line and it was then when I added
those lines myself.

So I can probably remove that last line I add to the fpc.cfg from my
script.

----------------------------------------------------------------------
Thausand · 2025-09-04 08:06

Quote from: rvk on September 04, 2025, 09:56:01 amI'm not sure if
that's always been the case. Could it be that the addition of "# path
to the gcclib" by fpcmkcfg???
No always be case but (recent) fpcmkcfg now make gcc path (depend on
what use template, default template make gcc path).

----------------------------------------------------------------------
rvk · 2025-09-04 08:27

Quote from: Thausand on September 04, 2025, 10:06:25 amQuote from: rvk
on September 04, 2025, 09:56:01 amI'm not sure if that's always been
the case. Could it be that the addition of "# path to the gcclib" by
fpcmkcfg???
No always be case but (recent) fpcmkcfg now make gcc path (depend on
what use template, default template make gcc path).
Yes, I see my script (from before 2016) used to use samplecfg (not
fpcmkcfg).

I switched to fpcmkcfg much later and I could have removed that line
from my script.

----------------------------------------------------------------------
Thausand · 2025-09-04 08:50

@rvk:
Thank for repeat message. I see, I have make cross-post sorry for
possible confuse.