Frank,
thank you for your help. Using the right argument syntax solves the problem.
BTW, I found another problem (or feature?):
If you type
gpc -L. -lmylib myprog.pas
the compiler generates an ld command with "-lmylib" inserted before the myprog binary. So external subroutines called in myprog are not resolved because the loader processes mylib first. To get the link working I typed
gpc -L. myprog.pas -lmylib
This looks strange to me, and I think the first format works with all c compilers.
Peter
Frank Heckenbach frank@g-n-u.de am 09.09.99 00:00:11
An: gpc@gnu.de Kopie: (Blindkopie: Peter Dietrich/SYNSTAR/DE) Thema: Re: GPC BUG? or how to use unit-path
pdietrich@synstar.de wrote:
The --unit-path option does not work (or maybe I don't know, how it works). The following program "mainprog" uses a unit in directory ..\test-units. I tried:
gpc --unit-path ..\test\units mainprog.pas
There's an `=' missing after the `--unit-path'. (The GNU compilers treat their command-line arguments differently than most other GNU tools, so you can't omit the `=' after long options...)
Frank
-- Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html
________________________________________________________________________________________
This communication contains information which may be confidential. It is for the exclusive use of the intended recipient. If you are not the intended recipient, please note that any distribution, copying or use of this communication or the information in it is prohibited. If you have received this communication in error, please notify us by email or by telephone on ++49 6151 989 0 and then delete the email and any copies of it.