Prof A Olowofoyeku (The African Chief) wrote:
On 15 Feb 2006 at 16:24, Waldek Hebisch wrote:
[...]
BTW. When testing gpc it us usefull to give `--enable-checking' option to `configure' -- the compiler build in such way performs extra internal checks (the checks make the compiler slower and larger, so they are disabled by default).
This doesn't advance the situation very much - I still can't find the source of the problem.
On the positive side, the snapshot passes the testsuite, with only these problems:
TEST avo7.pas: ./avo7.pas:5: warning: identifiers should not start with an underscore failed
For this one we have to modify the C compiler. I you type: gpc -v --gnu-pascal -Wno-underscore avo7.pas
I see:
Reading specs from /usr/local/lib/gcc/x86_64-unknown-linux-gnu/3.4.4/specs
as the first line. The specs file should contain the following blob: *cc1_options: %{pg:%{fomit-frame-pointer:%e-pg and -fomit-frame-pointer are incompatible}} %1 %{!Q:-quiet} -dumpbase %B %{d*} %{m*} %{a*} %{c|S:%{o*:-auxbase-strip %*}%{!o*:-auxbase %b}}%{!c:%{!S:-auxbase %b}} %{g*} %{O*} %{f*&W*&pedantic*&w} %{std*&ansi&trigraphs} %{v:-version} %{pg:-p} %{p} %{undef} %{Qn:-fno-ident} %{--help:--help} %{--target-help:--target-help} %{!fsyntax-only:%{S:%W{o*}%{!o*:-o %b.s}}} %{fsyntax-only:-o %j} %{-param*}
where the `%{f*&W*&pedantic*&w}' part is the crucial one
TEST prep1a.pas: f:/mingw/lib/libmingw32.a(main.o):main.c:(.text+0x106): undefined reference to `WinMain@16' collect2: ld returned 1 exit status failed compile: prep1a.pas
This one is spurious, because the `WinMain@16' complaint is unrelated to GPC.
This is most likely problem in the test. But it is not entirely suprious. The intent of the test is to check that running the compiler directly (`gpc.exe') is equivalent to running it in stages. I was mostly concerned with preprocessor here, but additionaly it tests that command line handling works as intended. But apparently on Mingw32 it does not work that way. Most likely, the test is garbling command line (or Mingw32 needs some extra twists), but there is also a tiny chance for compiler bug (maybe the compiler is misunderstanding the command). Could you add `-v' to the compiler options in the `prep1a.cmp' script and post the output?