Hi all,
I have found a couple of bugs after downloading this last version
1) A minor one, already present in the previous beta (january): the specs file is not correct. It seems to be the one used to cross-compile to DOS in your system. The correct one is contained in the gcc2.8.1 distribution of djgpp v2.02 and I have attached it for reference.
2) more serious a new bug (not present in the previous beta) has popped up in the automake process. It occurs when an unit is referred to both directly in the program and indirectly in an other unit as in the following example:
----------------------------------------- file bug.pas ----------------------------------------- program bug; uses u,uu; begin writeln(O,K); end.
------------------------------------------ file u.pas ------------------------------------------ unit u;
interface uses uu; var O:string[2] = 'O';
implementation end.
---------------------------------------- file uu.pas ---------------------------------------- unit uu;
interface var K: string[2] = 'K';
implementation end.
------------------------------------- compiled with redir -o bug.out -eo gpc -v -g --automake -o bug.exe bug.pas
gives the attached bug.out file
The error is in the link stage. The files u.o and uu.o are not included in the ld command (as they were in the previous beta). If I include them explicitly with
gpc -v -g --automake -o bug.exe u.o uu.o bug.pas all is correct
Hope this helps
Maurice
Hi!
Maurice Lombardi wrote:
Subject: bugs in gpc-19990530-i386-pc-djgppv202.zip
^^^^ That's a typo, sorry. The correct name is gpc-19990430.
- A minor one, already present in the previous beta (january): the specs file is
not correct. It seems to be the one used to cross-compile to DOS in your system. The correct one is contained in the gcc2.8.1 distribution of djgpp v2.02 and I have attached it for reference.
I corrected the errorneous "*cross_compile: 1" and introduced a mechanism to keep this correct automatically. Thanks.
- more serious a new bug (not present in the previous beta) has popped up in the
automake process. It occurs when an unit is referred to both directly in the program and indirectly in an other unit as in the following example:
The bug does not (no more?) occur with my current GPC (under Linux), so there is motivated hope that it will be fixed in the next snapshot.
I added your test program to our testsuite (maur6) to ensure this.
Thanks,
Peter