Hello.

Is it possible to sent new-other parameters to the linker ? Without the use of *-k*<some_paramter>, fpc sent this to the linker:

[5.227] (9017) Using util /usr/bin/ld
[5.227] Executing "/usr/bin/ld" with command line "-b elf64-x86-64 -m elf_x86_64 --dynamic-linker=/lib64/ld-linux-x86-6 4.so.2 -s -L. -o ./test ./link.res"

Using the *-k* parameter, this is sent (with *-ksomething -kotherting*):

[5.224] (9017) Using util /usr/bin/ld
[5.224] Executing "/usr/bin/ld" with command line "-b elf64-x86-64 -m elf_x86_64 *something* *otherthing* --dynamic-linker= /lib64/ld-linux-x86-64.so.2 -s -L. -o ./test ./link.res"

You may see that the parameters "something" "otherthing" are inserted afterelf_x86_64.

But how to sent totally custom parameters, without those given by fpc ?

Thanks.

-----
Many thanks ;-)

If you use -s the compiler will not link your program but leave a script "ppas.sh" that you can edit and run manually to assemble and link your program. Also it leaves a link.res file that if you really want to you can edit.

Regards,

Andrew

I've had no problem with e.g.

export OPT='-k-t -k--reduce-memory-overheads -k--no-keep-memory'

Andrew Haines wrote

Excellent, it is even better that my wishes.

Many thanks Andrew.

Fre;D

-----
Many thanks ;-)

I've had no problem with e.g. export OPT='-k-t -k--reduce-memory-overheads -k--no-keep-memory'

Ha, I will try this one too.

Thanks Mark.

Fre;D

-----
Many thanks ;-)

fredvs wrote

> I've had no problem with e.g. > export OPT='-k-t -k--reduce-memory-overheads -k--no-keep-memory' Ha, I will try this one too.

For completeness, I've re-read your OP several times and there could be a problem inserting options in a /specific/ /place/ in the ld command line (i.e. immediately before the new/output file), should this be required.

In this case I think the only realistic thing to do would be to use Andrew's suggestion of intercepting ppas.sh, anything else is venturing into Jonas territory :-)