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

2012-03-21 Thread Henry Vermaak
On 20 March 2012 22:42, peter green plugw...@p10link.net wrote: 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

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

2012-03-21 Thread Marco van de Voort
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.

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

2012-03-21 Thread Jonas Maebe
On 20 Mar 2012, at 23:42, peter green wrote: 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.

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

2012-03-21 Thread peter green
Jonas Maebe wrote: The compiler should find the crt*.o files on its own, especially if you create a special compiler binary for the hard float ABI (there is no point in creating a special binary if you still need to separately specify a bunch of additional options to get the correct

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

2012-03-20 Thread peter green
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