I have just downloaded the test suite to try and resolve my problem with gpc that I posted earlier.
The output from the test suite follows:
$ make rm -f *.dat *.o *.s *.i *.gpi *.gpd *.gpc core a.out stderr.out *.exe testmake.tmp dummy.c dummy.pas dummy.out diff_cr*.tmp fixcr fixcr.exe rm -f todo/a.out todo/*.exe todo/*.o todo/*.s todo/*.i todo/*.gpi todo/*.gpd todo/core GP= PC="gpc" PFLAGS=" --autobuild -g -O3 -W -Wall -Wno-unused " PFLAGS_NO_PATHS="-g -O3 -W -Wall -Wno-unused " SRCDIR="." TEST_MAKE_FLAG=test-make-flag "./test_run" "*.pas" | tee test_log | "./test_sum" -d /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../../i686-pc-cygwin/bin/ld: crtbegin.o: No such file: No such file or directory /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../../i686-pc-cygwin/bin/ld: crtbegin.o: No such file: No such file or directory ./test_run: fatal: cannot compile a simple program Nothing was run.
My problem seems to be due to the gpc/gcc distribution!
Best regards, Chris.
On 28 Dec 2005 at 20:25, Chris Hicks wrote:
It looks like a version issue. gcc-3.3.3 comes with a crtbegin.o but 3.4.4 (at least the Cygwin version) does not have a crtbegin.o.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/
On Wed, 28 Dec 2005, Chris Hicks wrote: [..]
My problem seems to be due to the gpc/gcc distribution!
Try gpc -v and gcc -v to get the paths to the specs file. In the same directory as the specs file there should be 5 crt support files ending in ".o". One word of caution - the support files from gcc-3.3.3 may not be compatable with those from gcc-3.4.4 so don't just copy one to the other.
If you want to try building gpc yourself since you have gcc-3.4.4 use a recient gpc source, gcc-3.4.4 source, the default prefix of /usr/local, and --enable-languages=c,pascal. You can do a "make" instead of "make bootstrap" to save time.
Hope this helps, Russ
On 28 Dec 2005 at 18:39, Russell Whitaker wrote:
[...]
I have built gpc-20051116 for Cygwin (based on gcc-3.4.4), and it can be found here: http://www.gnu-pascal.de/contrib/chief/win32/cygwin/
There are some testsuite failures - mainly to do with anything that uses Crt (something with Cygwin ncurses (again)). But there are also these three failures, that have nothing to do with Crt: TEST fjf1042b.pas: failed TEST fjf1042c.pas: failed bc, defgh TEST prep2p.pas: 10a11,13
failed
I will be looking into the Crt issue. I am sure it is not a big deal.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/
On 29 Dec 2005 at 9:42, I wrote:
[...]
I will be looking into the Crt issue. I am sure it is not a big deal.
It is indeed a simple thing. Install PDCurses - you can get sources and precompiled binaries here: http://www.gnu-pascal.de/contrib/chief/win32/cygwin/
Add the pdcurses "include" and "lib" directories to the compiler's search path ("-I" and "-L" respectively), and all will be well.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/
Prof A Olowofoyeku (The African Chief) wrote:
prep2p.pas is just expects too much: it tests if Pascal and C have the same set of predefined preprocessor symbols. But to handle things like `_cdecl', `_fastcall' or `_stdcall' we would be forced to look at C options which otherwise make no sense for Pascal. So you can disregard this failure (I will remove the offending symbols from the test).
-
Chris Hicks -
Prof A Olowofoyeku (The African Chief) -
Russell Whitaker -
Waldek Hebisch