Greetings,

I have been trying to cycle a new Win32 compiler so that I can make a complete Lazarus distro which includes the compiler.

I have the 1.9.2 binary release and am trying to cycle a new compiler from CVS code. It fails at various points. First it fails at rtl/win32/dos.pp not knowing what to do with threadvar.

If I comment that out it then blows up on objpas/math.pp.

I know that others are using compilers built from CVS so what the heck am I doing wrong?????

Any help would be appreciated since we want to do a Win32 binary release sometime this week.

These are known problems.
You must start with a 1.0.10 compiler when you create a new 1.9.X compiler. Some older (even quite recent) 1.9.x versions won't work.

Michael.

These are known problems. You must start with a 1.0.10 compiler when you create a new 1.9.X compiler. Some older (even quite recent) 1.9.x versions won't work.

Hmmmm. I was trying the same thing last week before my Win32 system crashed and was getting similar problems when trying to use 1.0.11. If I remember correctly it was calling for the assembler with a different name and other problems.

In any event I try using my 1.0.11 version and if that fails I drop back to the 1.0.10.

Thanks.

oh, so if i've already built / installed cvs version, then have to remove that and re-install 1.0.10 to build updated cvs?

Normally we see to it that the compiler and RTL can be cycled with the last official release. This has never been a problem, as far as I can remember.

Michael.

Yes, but no complete reinstall is necessary, only the 1.0.10 ppc386.exe.

So next time before you install 1.9.x, save the old (1.0.10) ppc386.exe. For example rename it to ppc386-release.exe.

HTH,
Vincent.

i remembered to keep a copy of the zip file for 1.0.10 handy so it wasn't that big a deal but this tip makes things even easier ... :)

went so far as to completely reinstall 1.0.10 just to be on the safe side, and i'm still getting the same error I was w/ the cvs compiler i had been using ...

make -C image clean
Makefile:154: *** The Makefile doesn't support target win32, please run fpcmake first. Stop.
make[2]: Entering directory `C:/CVS/fpc/fcl/image' make[2]: Leaving directory `C:/CVS/fpc/fcl/image'
make[1]: *** [image_clean] Error 2
make[1]: Leaving directory `C:/CVS/fpc/fcl'
make: *** [fcl_distclean] Error 2

this is the error message i get when trying a "make distclean" in the directory to which i fetched the fpc cvs sources

This Makefile (/fpc/fcl/image/Makefile) is only for linux. It needs to be generated again (by fpcmake), but then for all supported platforms.

HTH,
Vincent.

My mistake. Fixed.

Michael.

Fixed.

Thanks, but ATM fpwritetga.pp doesn't compile, due to missing KeyIndentification and FromWord in TFPWriterTarga.SaveHeader

Regards,
Vincent.

And again fixed... This is becoming a d�j� vu :-)

Michael.

Michael A. Hess wrote

.. I'll drop back to the 1.0.10.

Installed 1.0.10 and it built everything just hunky dory.

Now I have a question about the size of the exe.

After it is built the size is 1.3 meg.

I tried to run stripw on it but it doesn't reduce the file really jump to that size or am I just being stupid and not using stripw correctly.

stripw ppc386.exe

The make procedure runs UPX on it, so I would be surprised if stripw could do some more packing after that :-)

Michael.

From: "Michael Van Canneyt"
To:
Subject: Re: [fpc-pascal]Can't seem to cycle a new Date sent: Wed, 3 Mar 2004 09:10:36 +0100

1.3 MB is the size of the executable _without_ compressing with UPX. This IMHO means that either UPX wasn't found (this could be checked in make output probably), or the chosen make target doesn't do the compression at all (I don't know whether there are such targets for Win32, but it's possible).

Tomas

Mmmyes. I did some cheking: the UPX is used only when doing a 'make install'
The executable is then about 800K on my machine.

Maybe the -Xs option is used to strip unused symbols? It could be that this option is left in some config file ?

Michael.