At the of the top fpc Makefile, it says:
Don't edit, this file is generated by FPCMake Version 1.9.8 [2005/02/07] How and when does that generation get done?

All of the Makefiles use "TAROPT=vI" to compress with bzip; the gnu tar changefile indicates that "I" was superseded by "j" on 2000-10-23. The attached patch changes all "vI" to "vj".

I've been battling to "make pdf". It almost succeeded when I made a symlink from ...fpc/rtl/unix/classes.pp -> ...fpc/rtl/linux/classes.pp, failing on rtl.pdf with: If you really absolutely need more capacity,
you can ask a wizard to enlarge me.

Here is how much of TeX's memory you used:
32082 strings out of 95437
529481 string characters out of 1190234
167465 words of memory out of 1000001
14921 multiletter control sequences out of 10000+50000 59183 words of font info for 66 fonts, out of 500000 for 1000 14 hyphenation exceptions out of 1000
39i,12n,49p,1567b,5001s stack positions out of 1500i,500n,5000p,200000b,5000s 22628 PDF objects out of 300000
18641 named destinations out of 131072
16 words of extra memory for PDF output out of 65536 ! ==> Fatal error occurred, the output PDF file is not finished! The symlink is not an acceptable solution, of course, but it helped get a result. The makefile should default to a suitable "classes.pp", and should cater for adequate memory for document conversion.

I really want html documentation, but I can't get any action at all out of the "make -C docs l2h" which is recommended by "make -C docs help", or the "make html" recommended by ...fpc/install/INSTALL. I'm hoping that "html" will fall into line if I get "pdf" going.

Tips or suggestions would be appreciated.

Thanks,

Bob Barry

At the of the top fpc Makefile, it says: Don't edit, this file is generated by FPCMake Version 1.9.8 [2005/02/07] How and when does that generation get done?

I found fpcmake. I would have found it sooner if the message at the top of the top Makefile had not capitalized the first four letters of its name. Pascal is not case sensitive, but unix "find" _is_. The message uses "TitleDate"; if it were changed to use "lowercase(TitleDate)", the message would be more accurate.

Are the makefiles in cvs kept up-to-date, or should users run fpcmake after updating from cvs?

All of the Makefiles use "TAROPT=vI" to compress with bzip; the gnu tar changefile indicates that "I" was superseded by "j" on 2000-10-23. The attached patch changes all "vI" to "vj".

The "vI" comes from fpcmake; the attached simple patch fixes it.

Thanks,

Bob Barry

One could argue the tool name is FPCMake. The tool executable is called fpcmake. Unix find has a -iname search option for searching case sensitve.

Are the makefiles in cvs kept up-to-date, or should users run fpcmake after updating from cvs?

As a rule yes. Usualy users don't have to run fpcmake, unless they change the Makefile.fpc.

The fpcmake.inc file is generated by data2inc from fpcmake.ini.

Regards,
Vincent.

Vincent -

Thanks - revised patch is attached.