I downloaded the latest snapshot and wish to recompile the fpc compiler for G032v2. I found an old doc that says to:
cd compiler
make cycle

This obviously will not work since FPC has fpcmake and not make. There is also no makefile called cycle in the compiler folder. Can someone tell me how to completely recompile the fpc?

regards,
Andreas

AFAIK, fpcmake is another beast: it creates a Makefile based on infos in Makefile.fpc

"make cycle" should call the "make" executable, which reads "Makefile" in the current folder and does stuff for the target "cycle" defined in "Makefile".

however, never tried the go32v2 thing. only doing it on linux ..

http://www.freepascal.org/moreinfo.html contains a link to the Building FAQ http://www.stack.nl/~marcov/buildfaq.pdf

Where would I download the GNU make.exe? It does not come with FPC.

It does. However only with the releases, not with the snapshots.

Suggest you read these links - but from memory this is what you do. As was said before the utils are not included in snapshots- usually it's just the minimum there.

A) you need to download the latest go32v2 release which is 2.0.2 eg from ftpmaster.freepascal.org or another ftp site, from /pub/fpc/dist/i386-go32v2-2.0.2/

You then install this, and this gives you the correct version of all of the gnu utils you need and the released compiler that's used to start the make. The utils include make & ld - some others are used in the make too

B) Then you download the latest v2.1 source from /pub/fpc/snapshot/v21/source/fpc.zip & unzip it into a suitable directory, or get latest sources from svn if you can use it. Then, with the utils from step A in your path you do the 'make cycle' in ...\compiler & away you go. As was explained before, the makefiles are generated in fpc by another program and are included in the source...

Of course you can use B for making the latest v2.0 (ie v2.0.3) as well, with suitable directory name change above to v20...

BTW a new release 2.0.4, with a load of bug fixes, updates, is being prepared for release within next weeks - we are currently on rc2.

Let us know if there are any problems & we may be able to use these to fix problems in the documentation for 2.0.4.

Regards John

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

Thanks for the clear instructions. This should really be in the FAQ or Wiki.

Just a few questions:
- Will the 2.0.x tree be integrated into the 2.1.x tree?
- Why are there two branches?
- To integrate threading into DOS should I use 2.0.x or 2.1.x?

Regards,
Andreas

No. It's rather the reverse: fixes done in 2.1 are merged back to 2.0

- Why are there two branches?

To keep new development (i.e. things that fall outside of fixes) out of 2.0.

- To integrate threading into DOS should I use 2.0.x or 2.1.x?

2.1.x because 2.0.4 is the last 2.0 release.

Michael.

Michael Van Canneyt wrote

2.1.x because 2.0.4 is the last 2.0 release.

All new development is done in trunk or a branch of trunk. If things prove that they are working, they are merged to fixes.

I have a problem compiling the compiler. After a lot of compilation it attempts to compile pp.pas and I get the following error:

    pp.pas(213,1) Error: Entrypoint start not defined.

Regards,
Andreas

Andreas Berger wrote

I have a problem compiling the compiler. After a lot of compilation it attempts to compile pp.pas and I get the following error: pp.pas(213,1) Error: Entrypoint start not defined.

I downloaded todays snapshot and had the same problem. Then I compiled using "make all" + "make install" instead of "make cycle" and it worked. Is this correct? What does "make cycle" do exactly?

There is at least one difference.
If you do make cycle in the compiler directory, the fpc.cfg file is used. If you do make all or make compiler_cycle in the fpc source directory (that contains a compiler subdirectory), then no fpc.cfg file is used.

So maybe you should try make cycle OPT="-n"

Vincent

This is a known error - I get it too - but I only get when using the v2.1.1 compiler to start make. Do you get it when starting with the v2.0.2 release compiler released too? What about trying a snapshot of v20 compiler eg base_go32_v20.zip or similar.

You can get more info with "opt=-va" on CL - If there is any more useful info in that send the lines to us.

What system are you using for these makes? Dos? Win9x?

Regards John

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

I am using the v20 base compiler with the v21 source. It should create a v21 compiler.

I get the same error compiling under DOS, Win98 and Win2K

Regards, Andreas

Sorry, it gave the same error.

Andreas Berger wrote

I am using the v20 base compiler

The only supported bootstrapping compiler is the last release compiler, i.e. 2.0.2.

That is what I am using.

I assume you're compiling from trunk sources, right? Then we probably have some bug in trunk compiler (binary writer/internal linker?). There's a parameter for forcing external linker (in trunk compiler, not 2.0.2), you can try that.

I can have a look at it later, but probably not before 2.0.4 is out.

Tomas

No wonder. ;-) When using "make all", the new
(2.1.1) compiler is compiled using the starting
compiler (2.0.x). "Make cycle" tries to make sure
that the created compiler is still useable, at
least that useable that it can still build
itself. It does so by doing the same thing in a
cycle:

1) RTL and compiler (ppc1.exe) are compiled using
the starting compiler.

2) Everything except ppc1.exe is cleaned, RTL and
compiler (ppc2.exe) are compiled using ppc1.exe.

3) Everything except ppc2.exe is cleaned, RTL and
compiler (ppc3.exe) are compiled using ppc2.exe.

4) ppc2.exe and ppc3.exe are compared - they
should be equal. If they are the same, ppc3.exe
is renamed to ppc386.exe.

5) If you build more than just the compiler (e.g.
snapshot or release - i.e. this last step isn't
part of "make cycle" any more), the newly created
ppc386.exe is used for compilation of RTL, FCL,
FV, packages and IDE.

Tomas

So you mean that the newly created compiler is giving the error?

Andreas

Specifically, with ppc1.exe (which is 2.1.1
compiler already if working with 2.1.1 sources) -
you should be able to see this in the log/make
output.

Tomas

Ok, the ppc1.exe was created and but it couldn't create ppc2.exe. I'll start developing on the 2.0.x branch until this is resolved. All I do should be readily transferable to 2.1.x later

Andreas