Adriaan van Os wrote:
There is something special with --param, --param exists, but -fparam obviously not.
[G4:~/gnu/testgpc/adriaan] adriaan% gpc -c hello.pas --param ggc-min-heapsize=0 [G4:~/gnu/testgpc/adriaan] adriaan% gpc -c hello.pas -fparam ggc-min-heapsize=0 gpc: ggc-min-heapsize=0: No such file or directory gpc1: error: unrecognized option `-fparam'
[G4:~/gnu/testgpc/adriaan] adriaan% gcc -c hello.c --param ggc-min-heapsize=0 [G4:~/gnu/testgpc/adriaan] adriaan% gcc -c hello.c -fparam ggc-min-heapsize=0 gcc: ggc-min-heapsize=0: No such file or directory cc1: error: unrecognized option `-fparam'
The GCC docs list --param as "--param" where most other arguments are given in the "-f" form (the rationale behind it is unknown to me,
Also to me. I just know that some GCC people have rather strong opinions on these matters (some seem to think it's the end of civilization that GCC supports `--' as an alternative to the good old `-f' at all) ...
Now, here is the problem, --automake changes any "--" argument into a "-f" argument ...
The change is necessary internally for comparison with the list of GPC options, but it shouldn't be necessary to (and in fact probably better, anyway, not to) pass the changed options to the sub-process.
Try this patch (please test with various options and in various situations).
Frank