make ... OVERRIDEVERSIONCHECK=1
Last error message:
make: *** [build-stamp.i386-win32] Error 2
using the ppc386 file I tried to compile a simple hello world program.
but I get a fatal error saying that it cannot find the systems unit needed by my hello world program.
ok, I found an fpc.exe executable created under the utils folder. and I used a fpc.cfg file I found under a FPC/3.02 build, I changed the code to point to my new build of 3.0.4.First you write compile new 3.0.4 use old 3.0.4 and use version check override. This write make 3.0.4 fail. That mean new 3.0.4 not complete (that why miss unit system).
but even using this file I still get a fatal error saying that it cannot find the system unit needed by my hello world program.
when I do a search for system.pp or system.pas its not under any win32 or i386 folder. there is a systems.pp, but not a system.pp or system.pas.
can there be an error in the compilation of the i386 build or something?
I did do a make install.... I want to know in what folder does the executable gets placed.
I was expecting a fpc.exe, I found a ppc1.exe, ppc2.exe, ppc3.exe and ppc386.exe file.
using the ppc386 file I tried to compile a simple hello world program.
but I get a fatal error saying that it cannot find the systems unit needed by my hello world program.
any help?
I did do a make install.... I want to know in what folder does the executable gets placed.
Not entirely correct. The fpc.exe only handles the -P and -V (version suffix) options (and -Xp to add a specfic search path for the ppcX). Everything else is passed as is to the determined ppcX which also handles the configuration file.using the ppc386 file I tried to compile a simple hello world program.
but I get a fatal error saying that it cannot find the systems unit needed by my hello world program.
I'm no expert but IIRC fpc.exe is a wrapper that, among other things, read its configuration file, builds the proper command line and calls the corresponding ppc*.exe. If you call ppc386 yourself you'll have to pass to it all the various options that fpc reads from it config file, among them the libraries search path, units search path, etc.; otherwise you get errors like that.
In short: use fpc.exe unless you're very, very sure of what you're doing. :)