[fpc-devel] Cross-compiling and warnings from linker

Sergey Organov sorganov at gmail.com
Tue Nov 23 17:17:23 CET 2021

Tomas Hajny via fpc-devel
<fpc-devel-PD4FTy7X32k2wBtHl531yWD2FQJk+8+b at public.gmane.org> writes:

> On 2021-11-23 13:17, Sergey Organov via fpc-devel wrote:
>> Tomas Hajny via fpc-devel
>> <fpc-devel-PD4FTy7X32k2wBtHl531yWD2FQJk+8+b at public.gmane.org> writes:
>>> On 2021-11-22 16:46, Sergey Organov via fpc-devel wrote:
>>>> Jonas Maebe via fpc-devel
>>>> <fpc-devel-PD4FTy7X32k2wBtHl531yWD2FQJk+8+b at public.gmane.org> writes:
>  .
>  .
>> The compiler will still read only 2 configuration files at most, the
>> default for given instance of the compiler, and user's one.
> The user would still need to remember that the first one depends on
> the installation path (which may not be even known to the compiler on
> some platforms as far as I remember!). The user may not even
> care/remember where the compiler is installed under normal conditions.

Yes, in which case everything is supposedly already configured by the
administrator suitably.

>> I.e., compiler installed in /usr should *not* read
>> /usr/local/etc/fpc.cfg, only /etc/fpc.cfg. Compiler installed elsewhere,
>> say, in /abc/def/custom, should read /abc/def/custom/etc/fpc.cfg.
>> The idea of backing to read /etc/fpc.cfg if /abc/def/custom/etc/fpc.cfg
>> is not found for backward compatibility that I've suggested above now
>> doesn't look useful to me, as I can't figure a use-case where it would
>> help.
>> What is indeed confusing is sharing "system" configuration file between
>> native and cross- compiler.
> Why confusing?

Because it was not expected. I definitely can't point to any other user
tool that, being installed in /opt/cross/bla-bla-bla/, would read
configuration file from /etc/. Maybe I just didn't meet one yet.
However, GCC, being most close to FPC by its application, definitely
doesn't behave like that.


>> I'd suggest that at least -XR (if not the installation directory
>> itself) change the search path for configuration file.
>  .
>  .
> You should better read how the FPC option -XR is specified. What is
> the relation between 'Prepend <x> to all linker search paths' (see FPC
> help)
> and location of the configuration file?

Currently? Apparently very little. Specifications sometimes change

Anyway, I'm not trying to insist on anything or trying to re-design
configuration policy for FPC, just shared my feelings.

-- Sergey Organov

More information about the fpc-devel mailing list