Frank Heckenbach wrote:
Frank Heckenbach wrote:
Daniel Rudy wrote:
I am having problems getting GPC 2.1 20020510 to install correctly. It
compiles with no errors, but when I try to compile a program with it, I get numerous unresolved references when I try to use one of the builtin units. In this example, the unit is CRT. It seems that every routine that I use in CRT generates an unresolved reference.
Use `--automake' on the GPC command line.
If that doesn't help, please post exact error messages.
Frank
-- Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html
strata:/usr/local/lib/gcc-lib/i386-unknown-freebsdelf/2.95.3/units 1028 ->gpc --automake -DNOX11R6 crt.pas
When compiling a unit only, use `-c'. This will inhibit linking (as a unit alone cannot become an executable) and cause no linking errors. However, you normally don't habe to compile units yourself at all, since when you compile a program (with `--automake'), all units used will be compiled as well.
To compile a program that uses CRT, `gpc --automake myprog.pas' should work.
Frank
-- Frank Heckenbach, frank@g-n-u.de http://fjf.gnu.de/ GnuPG and PGP keys: http://fjf.gnu.de/plan (7977168E)
Interesting. Though wouldn't it be good programming practice to individually and periodicly build peices of your code to make sure that your syntax and spelling is correct? I realize that this falls under different programming philosiphies, but coming from a BP 7.0 environment, it was extreamly easy to do to just check things out to make sure that everything was ok.
Daniel Rudy wrote:
When compiling a unit only, use `-c'. This will inhibit linking (as a unit alone cannot become an executable) and cause no linking errors. However, you normally don't habe to compile units yourself at all, since when you compile a program (with `--automake'), all units used will be compiled as well.
To compile a program that uses CRT, `gpc --automake myprog.pas' should work.
Interesting. Though wouldn't it be good programming practice to individually and periodicly build peices of your code to make sure that your syntax and spelling is correct? I realize that this falls under different programming philosiphies, but coming from a BP 7.0 environment, it was extreamly easy to do to just check things out to make sure that everything was ok.
Sure, if you prefer this, you can do this (just use `-c' then).
Frank