[fpc-pascal] Compiling sources obtained via SVN

[Mark Morgan Lloyd]

brian wrote:
> I assume there's an expectation that the sources downloaded from trunk 
> should compile on all platforms?
> 
> I've just updated to 19505, and attempting to build on Linux Mint 9 
> 64-bit causes a few problems.
> 
> The first problem I see is that there are actually two makefiles in the 
> fpc directory, Makefile dated 31st Aug 2011 and Makefile.fpc dated 13th 
> Aug 2011.
> 
> However, unless I'm missing some switch or other, doing a
> 
> make distclean
> 
> followed by
> 
> make -f Makefile build
> 
> generates a LARGE number of unresolved references.
> 
> With apologies to anyone still on dial-up, the error messages are posted 
> below.
> 
> I do have v2.4.2-0 installed on my machine, this was from installing the 
> combined FPC and Lazarus .DEBs from sourceforge, but presumably the make 
> should be working with the files in the subversion tree?
> 
> 
> Brian.
> 
> <...>
> 
> /data2/sources/subversion/fpc/packages/gdbint/units/x86_64-linux/gdbint.o: 
> In function `GDBINT$_$TGDBINTERFACE_$__$$_GDB__INIT':
> gdbint.pp:(.text+0xfde): undefined reference to 
> `deprecated_create_breakpoint_hook'
> /data2/sources/subversion/fpc/packages/gdbint/units/x86_64-linux/gdbint.o: 
> In function `GDBINT$_$TGDBINTERFACE_$__$$_GDB_DONE':
> gdbint.pp:(.text+0x103f): undefined reference to 
> `deprecated_create_breakpoint_hook'
> /usr/lib64/libgdb.a(varobj.o): In function `construct_visualizer':
> (.text+0x83d): undefined reference to `_Py_NoneStruct'

So either sort out your libgdb, which is not part of FPC and needs to be 
copied into the build directory, or build with

make distclean
make NOGDB=1 all

I think that NOGDB is right, but I'm working from memory here. In 
general I build without libgdb at any sign of problems since it's only 
used in the fp (text) IDE, however I've successfully built it on all 
platforms here except ARM (not tested on x64 since I don't have one).

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]