[fpc-devel] passing options for the build process.

Marco van de Voort marcov at stack.nl
Wed Mar 21 09:24:40 CET 2012

In our previous episode, peter green said:
> The buildfaq claims that OPT= will add parameters to every compiler 
> commandline. Unfortunately it doesn't seem to actually do that. The 
> options are added when building the compiler and RTL but it seems they 
> aren't added when building fpmake.
> This is a problem for me as to successfully build fpmake on a multiarch 
> arm system I need to tell it where to find crti.o (it seems freepascal 
> can successfully build stuff linked against c libraries without finding 
> crti.o on some architectures but not others).
> For now i've created a symlink at /usr/lib/crti.o to 
> /usr/lib/arm-linux-gnueabihf/crti.o to make things work but i'd rather 
> not have to mess with my system in that way. Is there some way of 
> specifying options so that they actually get passed to ALL compiler 
> invocations in the build process?

Sounds like a fpmake bug. Please file a bugreport if you haven't done so.

More information about the fpc-devel mailing list