Hi,

I just installed free pascal/Linux in a local directory (/home/jork/usr/...) and it seems that fpc does *not* read ~/.fpc.cfg. It also seems it does not read ./fpc.cfg. After copying ~/.fpc.cfg to fpc.cfg in another directory and setting PPC_CONFIG_PATH to this directory it works. Am I doing wrong or is this really bad behavior of fpc?

Best regards,
Jork

It works correctly (tested with 1.0.6/1.0.7)

stat("ppc386.cfg", 0xbfffefb8) = -1 ENOENT (No such file or directory) stat("/home/michael/.ppc386.cfg", 0xbfffefb8) = -1 ENOENT (No such file or directory) stat("/etc/ppc386.cfg", 0xbfffefb8) = -1 ENOENT (No such file or directory) stat("fpc.cfg", 0xbfffefb8) = -1 ENOENT (No such file or directory) stat("/home/michael/.fpc.cfg", {st_mode=S_IFIFO|S_ISGID, st_size=0, ...}) = 0

BUT

if a file ~/.ppc386.cfg exists, then that will be read first (for compatibility with earlier versions) and ~/.fpc.cfg will *not* be read. So make sure that you remove ~/.ppc386.cfg

Michael.

Michael,

how did you got the trace? My fpc forks and I dont see the opened files. Here the detailed version output.

/home/jork/temp/pas> fpc -i
Free Pascal Compiler version 1.0.6

Compiler Date : 2002/04/30
Compiler Target: i386

This program comes under the GNU General Public Licence For more information read COPYING.FPC

Report bugs, suggestions etc to:

/home/jork/temp/pas>

Michael, how did you got the trace? My fpc forks and I dont see the opened files. Here the detailed version output.

I don't do fpc, I did ppc386 (fpc forks ppc386)
if you do 'strace -f fpc', it will follow (f) the forks and you can simply use fpc.

Michael.

Michael,

I don't do fpc, I did ppc386 (fpc forks ppc386) if you do 'strace -f fpc', it will follow (f) the forks and you can simply use fpc.

Ok, I got it. Someone created /etc/ppc386.cfg... But, wouldn't it be better to read a user-specific config file despite a global one exists in /etc?

Best regards,
Jork

From:
Date sent: Thu, 8 Aug 2002 13:08:52 +0200 (DFT) To:
Subject: Re: [fpc-devel]free pascal config files Send reply to:

Doesn't it work if you name your local config file the same way as the global one is named (i.e. ppc386.cfg)?

Tomas