Good day,

After tried to build the fpcbuild.zip version, by executing the commad make build or make, I received the following error message: make: -iVSPTPSOTO: Command not found

Please how can I fix it?

You first have to install the latest (binary) release of FPC. FPC is self-hosting and requires itself to bootstrap (just like you need a C compiler to bootstrap most other C compilers).

Jonas

You've probably not got a runnable fpc binary.

Please remember to tell us what OS etc. you've got with any questions if you want sensible answers.

am running on debian

Good man. If there's a runnable fpc in your path (this is a shim that sorts out some extra settings for the ppc binary) and you still have problems, then try an explicit PP setting e.g.

export PP=/usr/local/bin/ppc386
make OPT='-O- -gl -Xs-' all

runnable fpc, you mean fpc-2.6.0 installed?

export PP=/usr/local/bin/ppc386 make OPT='-O- -gl -Xs-' all

I specifically mean a binary called fpc, e.g. /usr/local/bin/fpc (or some other path of your choice). Where you got it from is your business.

Well, this last statement is probably worth a slight extension - in general, the three basic options for getting the starting compiler binary are:

1) Install the last official release (as already suggested in your previous statement) - obviously the easiest option if possible for your particular case.

2) Get a bootstrap compiler binary for your platform (e.g. ftp://ftp.freepascal.org/pub/fpc/dist/2.6.0/bootstrap/).

3) Cross-compile the compiler binary (if not available from either of the two previous options) on one of the architectures/platforms supported in the last release.

Tomas

Tomas Hajny wrote

Well, this last statement is probably worth a slight extension - in general, the three basic options for getting the starting compiler binary are:

[...]

2) Get a bootstrap compiler binary for your platform (e.g. ftp://ftp.freepascal.org/pub/fpc/dist/2.6.0/bootstrap/).

That should only be done if all else fails, because building with only a compiler binary available can easily fail for a variety of reasons.

Jonas

Thanks for the bootsrap link.

But I got another problem during linking process:
fp.pas(553,1) Error: Error while linking
fp.pas(553,1) Fatal: There were 1 errors compiling module, stopping Fatal: Compilation aborted
make[5]: *** [fp] Error 1
make[5]: Leaving directory `/home/erickom/fpcbuild/fpcsrc/ide' make[4]: *** [buildfp] Error 2
make[4]: Leaving directory `/home/erickom/fpcbuild/fpcsrc/ide' make[3]: *** [gdb] Error 2
make[3]: Leaving directory `/home/erickom/fpcbuild/fpcsrc/ide' make[2]: *** [ide_all] Error 2
make[2]: Leaving directory `/home/erickom/fpcbuild/fpcsrc' make[1]: *** [build-stamp.i386-linux] Error 2
make[1]: Leaving directory `/home/erickom/fpcbuild/fpcsrc' make: *** [fpcsrc/build-stamp.i386-linux] Error 2

Mark Morgan Lloyd wrote

> runnable fpc, you mean fpc-2.6.0 installed? >> export PP=/usr/local/bin/ppc386 >> make OPT='-O- -gl -Xs-' all

Apologies for my poor threading here, but a message got lost in the spam trap.

You've not put in enough context, but I'd guess that it can't find the libgdb library for the fp IDE (which not many people use, and I think that you've successfully built the main fpc compiler etc). Try setting PP as before, then

make NOGDB=1 OPT='-O- -gl -Xs-' all

the build process went successful.

it failed again during make install:
make rtl_distinstall FPC=/home/erickom/fpcbuild/fpcsrc/compiler/ppc386 ZIPDESTDIR=/home/erickom/fpcbuild/fpcsrc FPCMAKE=__missing_command_FPCMAKE make[3]: Entering directory `/home/erickom/fpcbuild/fpcsrc' make -C rtl distinstall
make[4]: Entering directory `/home/erickom/fpcbuild/fpcsrc/rtl' make -C linux all
make[5]: Entering directory `/home/erickom/fpcbuild/fpcsrc/rtl/linux' make[5]: Leaving directory `/home/erickom/fpcbuild/fpcsrc/rtl/linux' __missing_command_FPCMAKE -p -Ti386-linux Makefile.fpc make[4]: __missing_command_FPCMAKE: Command not found make[4]: *** [fpc_install] Error 127
make[4]: Leaving directory `/home/erickom/fpcbuild/fpcsrc/rtl' make[3]: *** [rtl_distinstall] Error 2
make[3]: Leaving directory `/home/erickom/fpcbuild/fpcsrc' make[2]: *** [installbase] Error 2
make[2]: Leaving directory `/home/erickom/fpcbuild/fpcsrc' make[1]: *** [installbase] Error 2
make[1]: Leaving directory `/home/erickom/fpcbuild' make: *** [install] Error 2

missing command fpcmake

Eric Kom wrote

it failed again during make install:

Please install the latest official release (as I recommended earlier on) rather than using only a bootstrap compiler, then it will work fine.

Jonas

..

missing command fpcmake

su, set and export PP, try again.

That will have no

Hi all,

I've made a little script to make and install FPC in a subdirectory with the standard hierarchy on Unixes and that runs quite good even if fpc is not yet installed... Maybe this can help!

Anyway, you've got it joined. Just copy it to your fpc source dir, run it that way :
PREFIX="opt/fpc" fpc.build.sh

When the process is terminated it gives more instruction about what have to be done to finish.

It's ready for cross compilation as you can give the target arch as the first parameter (Linux, x86_64, i686 or arm are the only supported by the script) but not tested yet.
The second (or fist if no arch is given) parameter is a libtool's destdir equivalent usefull for packaging. An interesting thing is to use PREFIX var to set installation prefix.

It's build arround a generic packaging script that we use on a distribution I'm co-developping so there may be unneeded test and or operations, particularly with documentation, man and info.

Regards,

having another release of fpc installed will make me have two version of fpc that really confused me during the compilation of lazarus. I only the trunk version of fpc.

That will cause you lots of headaches during the compilation of FPC instead. And you'll end up with multiple versions of FPC anyway as soon as the version number of trunk changes. Just specify the FPC version you want to use when compiling Lazarus instead, e.g. by adding "FPC=/usr/lib/fpc/2.7.1/ppc386" to your make invocation after compiling and installing the svn trunk version of FPC.

Jonas

As already suggested by Jonas (and also by me when giving it as the first option in my list of options), regular installation of the last release should be the first choice (and anything else is not supported). That said, possible workaround for your particular case would be using the newly created fpcmake binary (probably already built in fpcsrc/utils/fpcm/ before the step which failed for you) - either in its original place or by copying it elsewhere first; you can inform FPCMAKE of its location by adding
FPCMAKE=.../fpcsrc/utils/fpcm/fpcmake to the make command.

Still, I agree to Jonas that standard installation should be preferred over these workarounds (which are primarily intended for situations when the standard solution cannot be used).

Tomas

In our previous episode, Tomas Hajny said:

Specially since there are more such hidden dependencies, like data2inc

IOW there is a difference between the most minimal dependencies possible (e.g. for the first period after the initial bootstrap) and what is normal and supportable.

Normal and supportable is having the last release installed, use that to bootstrap trunk, and then crosscompile.