TOPIC:

Hi,

This might be something simple or stupid, but it is driving me a bit crazy. I have installed CT 4.10. It shows both the 32bit and 64bit compilers are installed and both are in ...fpc\bin\i386-win32 and ...fpc\bin\x86_64-win64 respectively.

When I setup the system for the 64bit compiler (with the correct 64bit make.exe and gdb.exe) it works fine. However, when I set it up for the 32bit compiler it complains there is no fpc.cfg.

I have checked both directories (...fpc\bin\i386-win32 and ...fpc\bin\x86_64-win64) and there an fpc.cfg in each. I have inspected both and they are correct, ie. one is for the 64bit compiler and one is for the 32bit compiler. So why does the system find the fpc.cfg in the 64bit directory yet cannot find it in the 32bit directory. I ran a previous version of Lazarus and it had no problems with the 32bit version.

This is really causing me some grief, we spent several days tracking down a DLL mismatch issue (64bit app vs 32bit dll) and now need to compile the app with the 32 bit compiler.

Any help GREATLY appreciated....

Kevin

Please Sir
give us more info

Did you has administrator privileges ?
Did you uninstall any previews Lazarus version ?
Did you check your "PATH" files ?

Hi,

Did you has administrator privileges ?

Yes

Did you uninstall any previews Lazarus version ?

Yes, when I did the install of 4.10 I did the remove old version and install new version option.

Did you check your "PATH" files ?

I assume they are correct since it works for 64bit and it (I think I have read) looks for the CFG file in the directory of the fpc.exe file. Where else should I look for PATH files?

Regardless, the Make.exe, DBG.exe, FPC sorces and Lazarus directories are all correct.
When I start lazarus it complains about no fpc.cfg file, but starts. Going to Tools>Options>File I get the same as I input to the Configure Lazarus Window:

Lazarus Directory: C:\CodeTyphon\Lazarus\
Compiler Path: C:\CodeTyphon\fpc\bin\i386-win32\fpc.exe
FPC source directory: C:\CodeTyphon\fpcsrc
Make Path: C:\codetyphon\fpc\bin\i386-win32\make.exe
Directory for building project: C:\codetyphon\lazarusTemp\

The debugger path is set to: C:\codetyphon\binGDB\win32\gdb.exe

There is nothing in the debugger Additional search path.

Thanks,
Kevin

Please Sir
Use CT Center "Remove and build ALL" procedure.
Save the building log file (txt), zip and post here.

Sorry, where is the log file? As soon as the build is finished it closes the window.

I still have the Cannot find FPC.CFG error with the 32 bit version.

EDIT: Well I sort of got round this by putting the 32bit fpc.cfg file into C:\CodeTyphon\Lazarus

And I can live with that, but it is sub-optimal. I have no idea why the setup can find: C:\codetyphon\fpc\bin\x86_64-win64\fpc.cfg yet cannot find: C:\codetyphon\fpc\bin\i386-win32\fpc.cfg when the FPC location is set to: C:\codetyphon\fpc\bin\x86_64-win64\fpc.exe and C:\codetyphon\fpc\bin\i386-win32\fpc.exe respectively?

Thanks,
Kevin

At least three threads about this problem...and no official reply.

Guys
we must understand the problem
please some one
1)-Open CT Center
2)-Execute action CodeTyphon->"Remove and Build all"
3)-After script finish, save building log txt (CommandBox page of CTC)
4)-zip and post here

1)


2)


3)

I've done that, but when the build etc finishes the command box disappears? I assume it is meant to stay there so I can copy the text to a file.

I will try it again, it takes some time which is why I do not sit around watching it and waiting for it to finish. But if the command screen disappears after completion again, I'm at a loss?

Cheers,
Kevin

On the right side of CommandBox
select: "Run Embedded"

See attached.....

The thought occurs to me, wouldn't it be just as easy, in the box that asks for the location of the free pascal compiler to have an option to ask for the CFG file. It could default to what was expected, but would give the user the option to browse for it. That would solve the problem would it not regardless of what any PATH statements said?

EDIT:

So after this last clean out and re-install same issue, BUT when I put the fpc.cfg file into C:\CodeTyphon\Lazarus (which worked before) I still get the fpc.cfg missing error - damn, back to unusable....

Cheers,
Kevin

In your building log all are OK

the Default fpc.cfg folder :

for Win32:
C:\codetyphon\fpc\bin\i386-win32\fpc.cfg

for Win64:
C:\codetyphon\fpc\bin\x86_64-win64\fpc.cfg

in your building Log lazarus read these fpc.cfg files...

My Suggestions:
1)Search and delete any other fpc.cfg from your PC (except from above folders)
2)try to start Lazarus from CT Center

for Win32:
C:\codetyphon\fpc\bin\i386-win32\fpc.cfg

for Win64:
C:\codetyphon\fpc\bin\x86_64-win64\fpc.cfg

And they are there, I can confirm that.

1)Search and delete any other fpc.cfg from your PC (except from above folders)

Done, the only FPC.CFG files are in the folders above.

2)try to start Lazarus from CT Center

That's how I often start it and have been since getting this problem (although starting from C:\CodeTyphon\Lazarus gives the same problem).

Regardless, after performing Steps 1 and 2 above there is no change, I get the same Error fpc.cfg is missing (but not when I set the compiler path to the 64bit compiler - then it works).

EDIT:

This is REALLY WEIRD.

1. The 32bit version of Lazarus works fine creating a 32bit exe (ie. it can find the fpc.cfg file)
2. The 64bit version of Lazarus cannot create a 32bit exe because it cannot find the fpc.cfg file for the 32bit compiler.

My options now are to use 64bit lazarus to create 64bit applications and 32bit Lazarus to create 32bit applications - a bit silly really, but the only option.

Cheers,
Kevin

So, my last suggestion:
-Check the permissions to FPC.CFG files and folders

cd C:\codetyphon\
ATTRIB /S /D -R -S -H *.*

Hi,

I will try that, but before I do let me predict it will have no effect because the 32bit version of Lazarus uses the same 32bit compiler and works fine without any permissions issues.

Trying now......

Nope, same Error fpc.cfg missing message with the 64bit Lazarus and the 32bit compiler....

Cheers,
Kevin

The same issues are also on Ubuntu.