Hi All,
I'm trying to link a program, that uses a couple of my own units already precompiled. So, I'm not specifying neither --automake nor --autobuild. Link editor ld reports error it can't find referenced symbols. There are two ways to go through this:
1. use autobuild facility - everything builds fine, or
2. supply object file names for gpc when linking - nightmare in case of advanced projects, though C works that way.
I'm using 20000714 version on Solaris 8 x86. I remember I had similar problems with unofficial April version.
I didn't find that in documentation, is it an unfixed bug?
On the other hand, Pascal units works different than C modules and special make tool is necessary. I remember Frank's posting on that. So, automake seems quite natural as default. Maybe there should be an option to turn it off instead? E.g. Free Pascal works so that it always runs in autobuild mode, at least one of its older versions I had.
Regards
Hello!
Mariusz Zynel wrote:
I'm trying to link a program, that uses a couple of my own units already precompiled. So, I'm not specifying neither --automake nor --autobuild. Link editor ld reports error it can't find referenced symbols. There are two ways to go through this:
use autobuild facility - everything builds fine, or
supply object file names for gpc when linking - nightmare in case of advanced projects, though C works that way.
[...]
I didn't find that in documentation,
info -f gpc -n "GPC Options"
is it an unfixed bug?
No, it's a feature. But this is not the first time it is reported as a bug, so ...
On the other hand, Pascal units works different than C modules and special make tool is necessary. I remember Frank's posting on that. So, automake seems quite natural as default. Maybe there should be an option to turn it off instead?
GPC's current behaviour is due to consistency with other GNU compilers and with Borland Pascal where you also have to give an option `/M' in order to get the effect of `--automake'.
However if we agree on this list that `--automake' should be the default, I wouldn't mind changing GPC that way.
Another solution: It is planned to distribute an external utility in the future which does the same as `--automake' and more. This will make GPC's internal `--automake' facility obsolete.
What do you think?
E.g. Free Pascal works so that it always runs in autobuild mode, at least one of its older versions I had.
"Autobuild" or "automake"? I'd consider "autobuild" a bug, "automake" a feature.
Peter
Peter Gerwinski wrote:
Another solution: It is planned to distribute an external utility in the future which does the same as `--automake' and more. This will make GPC's internal `--automake' facility obsolete.
Frank mentioned something already... I've been always told that good programming practice is to break every task into smaller, "selfcontained" tasks... less error prone.
E.g. Free Pascal works so that it always runs in autobuild mode, at least one of its older versions I had.
"Autobuild" or "automake"? I'd consider "autobuild" a bug, "automake" a feature.
It was autobuild... weird. No offense intended FP guys.
Regards
E.g. Free Pascal works so that it always runs in autobuild mode, at least one of its older versions I had.
"Autobuild" or "automake"? I'd consider "autobuild" a bug, "automake" a feature.
It was autobuild... weird. No offense intended FP guys.
I replied to the original msg from Peter to you Marius, instead of the group. Could you please forward my answer to the group?
Marco van de Voort (MarcoV@Stack.nl or marco@freepascal.org)
On 18 Jul 00, at 16:14, Peter Gerwinski wrote:
[...]
GPC's current behaviour is due to consistency with other GNU compilers and with Borland Pascal where you also have to give an option `/M' in order to get the effect of `--automake'.
The difference is that compiling a program that uses units with BP normally works even if you don't specify '/M', unless you have changed the interface of a used unit and the compiler cannot find the new things in the pre-compiled TPUs. With GPC on the other hand, my experience is that '--automake' is normally needed even when there are precompiled units and the interfaces have not changed. Thus, having the automake feature turned on by default seems quite sensible (and I am not sure why one would want to turn it off, except to use '--autobuild').
However if we agree on this list that `--automake' should be the default, I wouldn't mind changing GPC that way.
I vote for this.
Another solution: It is planned to distribute an external utility in the future which does the same as `--automake' and more. This will make GPC's internal `--automake' facility obsolete.
What do you think?
The utility is fine, but I think that just being able to type 'gpc foo.pas' is a good thing, even when 'foo.pas' uses other units.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) Author of: Chief's Installer Pro v5.22.1 for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm Email: African_Chief@bigfoot.com
-
Marco van de Voort -
Mariusz Zynel -
Peter Gerwinski -
Prof Abimbola A Olowofoyeku