Gpc April 1998

gpc@gnu.de

20 participants
35 discussions

Files
by berend＠beard.nest.nl 01 Feb '02

01 Feb '02

* Moved (from: gpc) by Berend de Boer using timEd 1.10.b3+. Peter Gerwinski wrote in a message to Berend de Boer: PG> I tried to use Extended Pascal "binding" to assign a file PG> variable to an external -- existing -- file. I just copied PG> the "Assign" pro- cedure by Berend as published in PG> borland2ep.doc. It does not always work: I often get a PG> runtime error saying that the file did not exist. If you can repeat it, compile with another Extended Pascal compiler, for example Prospero's one. If that fails too, there is really something wrong with the code. But I suspect gpc. You're using which OS? Groetjes, Berend (-: fido: 2:281/527.23 email: berend(a)beard.nest.nl

4 3

Re: Compiling problems when installing gpc-980420
by Igor Perisic 30 Apr '98

30 Apr '98

Hi Nick, I checked the core file that I found in p/rts where the compiling stoped. And here is what I get using the bt or backtrace command on the core file: (gdb) core-file core Core was generated by `gpc1'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/shlib/libc.so...(no debugging symbols found)...done. warning: Hit heuristic-fence-post without finding warning: enclosing function for address 0x12021105c This warning occurs if you are debugging a function without any symbols (for example, in a stripped executable). In that case, you may wish to increase the size of the search with the `set heuristic-fence-post' command. Otherwise, you told GDB there was a function where there isn't one, or (more likely) you have encountered a bug in GDB. #0 0x12021105c in ?? () (gdb) bt #0 0x12021105c in ?? () warning: Hit heuristic-fence-post without finding warning: enclosing function for address 0x1202261c8 Now the problem is that DEC doesn't deliver a "debugger" material for free so I am using gdb (I don't have the license for DEC's dbx). In my signal.h file 11 is segmentation fault as is also shown above. I have no idea what this heurisitic-fence-post is so I'll try to play with it. Thanks for the help though. I looked at using glibc... instead of libc but got this ugly message ;-) loading cache ./config.cache checking host system type... alpha-dec-osf4.0 *** The GNU C library is currently not available for this platform. *** So far nobody cared to port it and if there is no volunteer it *** might never happen. So, if you have interest to see glibc on *** this platform visit As you see I don't really want to go down that road for now... Hope the small bt can help though... Igor

1 0

Re: Compiling problems when installing gpc-980420
by Igor Perisic 30 Apr '98

30 Apr '98

Sorry Peter, I tried your fix up but I still end at the same place with exactly the same error message. What does that error 11 stand for? I checked gcc (version 2.8.1) and it was working fine so the "error" shouldn't come from there. I tried your fix up starting from the begining, that is deleting all the *.o files and reruning the make command. Thanks for your help .... Igor

2 1

Compiling problems when installing gpc-980420
by Igor Perisic 30 Apr '98

30 Apr '98

Hi all, I've been talking with Peter for a while now about my problems with installing gpc on my machine. After trying to put the 2.0 version, he "persuaded" me to look at the alpha version of 2.1 (which is supposed to be already more stable). I am running Digital Unix 4.0D on a Dec Alpha machine. I reinstalled gcc-2.8.1 in order to be able to build gpc-980420 (the latest version that is available). I edited the p/diffs/gcc-2.8.1.diffs to point to gcc-2.8.1 instead of gcc-2.8.0 and I edited a couple of lines in config-lang.in for the test about the version of gcc to require 2.8.1 instead of 2.8.0. Patched all the patches, installed the source at the correct place typed ./configure then cd p and ./configure (then edited a line in config.cache as it seemed to still want to use cc-E as the preprocessor to switch it to gcc -E) reruned ./configure and then launched make LANGUAGES=pascal in the source (gcc-2.8.1) directory. I get stuck at the compiling of rts-base.p and here is my error message. I included some previous lines since I get something weird with rts-string.c (which is compiled two steps before the rts-base.p): error> rts-string.c:632: warning: no previous prototype for `_p_val_medcard_nocheck' error> rts-string.c:633: warning: no previous prototype for `_p_val_longcard_nocheck' error> rts-string.c:662: warning: no previous prototype for `_p_val_shortreal' error> rts-string.c:663: warning: no previous prototype for `_p_val_real' error> rts-string.c:664: warning: no previous prototype for `_p_val_longreal' error> ../../xgcc -B../../ -c -DGPC -Wall -Wpointer-arith -Wmissing-prototypes -Wmissing-declarations -g -I. -I../.. -I/usr/users/igor/TEMP/gcc-2.8.1/p/rts/../.. -I/usr/users/igor/TEMP/gcc-2.8.1/p/rts/../../config rts-bind.c error> ../../xgpc -B../../ --automake -c -DGPC -Wall -Wpointer-arith -Wmissing-prototypes -Wmissing-declarations -g -I. -I../.. -I/usr/users/igor/TEMP/gcc-2.8.1/p/rts/../.. -I/usr/users/igor/TEMP/gcc-2.8.1/p/rts/../../config rts-base.p error> xgpc: Internal compiler error: program gpc1 got fatal signal 11 error> *** Exit 1 error> Stop. error> *** Exit 1 error> Stop. Using Peter's comments (from a previous email) I reran the last command with the following flags -v --automake=-v and here is the result: new command> # ../../xgpc -B../../ -v --automake=-v -c -DGPC -Wall -g -I. -I../.. -I/usr/users/igor/TEMP/gcc-2.8.1/p/rts/../.. -I/usr/users/igor/TEMP/gcc-2.8.1/p/rts/../../config rts-base.p messages> Reading specs from ../../specs messages> gpc driver version 980420(2.8.1) executing gpc version 2.8.1 messages> ../../gpc-cpp -lang-pascal -v -I. -I../.. -I/usr/users/igor/TEMP/gcc-2.8.1/p/rts/../.. -I/usr/users/igor/TEMP/gcc-2.8.1/p/rts/../../config -isystem ../../include -nocharescape -undef -D__GNUC__=2 -D__GPC__=2 -D__GNUC_MINOR__=8 -Dunix -D__osf__ -D__alpha -D__alpha__ -D_LONGLONG -DSYSTYPE_BSD -D_SYSTYPE_BSD -D__unix__ -D__osf__ -D__alpha -D__alpha__ -D_LONGLONG -D__SYSTYPE_BSD__ -D_SYSTYPE_BSD -D__unix -D__SYSTYPE_BSD -Asystem(unix) -Asystem(xpg4) -Acpu(alpha) -Amachine(alpha) -D__BITS_LITTLE_ENDIAN__=1 -D__BYTES_LITTLE_ENDIAN__=1 -D__WORDS_LITTLE_ENDIAN__=1 -g -Wall -D__LANGUAGE_C__ -D__LANGUAGE_C -DLANGUAGE_C -DGPC rts-base.p /tmp/ccaaabaa.i messages> GNU CPP version 980420(2.8.1) messages> #include "..." search starts here: messages> #include <...> search starts here: messages> . messages> ../.. messages> /usr/users/igor/TEMP/gcc-2.8.1/p/rts/../.. messages> /usr/users/igor/TEMP/gcc-2.8.1/p/rts/../../config messages> ../../include messages> /usr/local/include messages> /usr/local/alphaev56-dec-osf4.0d/include messages> /usr/local/lib/gcc-lib/alphaev56-dec-osf4.0d/2.8.1/include messages> /usr/include messages> End of search list. messages> ../../gpc1 /tmp/ccaaabaa.i -quiet -dumpbase rts-base.pas -g -Wall -version -famtmpfile=rts-base.gpc -fautomake=-v -o /tmp/ccaaabaa.s messages> GNU Pascal version 980420(2.8.1) (alphaev56-dec-osf4.0d) compiled by GNU C version 2.8.1. messages> xgpc: Internal compiler error: program gpc1 got fatal signal 11 Peter also told me to run it with the -dy or -dY to have more info on what is going. The results are identical to the one just described above. Word for word the messages are the same. I hope that there anyone out there that knows what is going on. As you can see, I am not an expert at this but I am looking forward to be able to continue to program in pascal. Thanks a lot in advance. Igor

3 2

Re: Compiling problems when installing gpc-980420
by Frank Heckenbach 30 Apr '98

30 Apr '98

Igor Perisic wrote: > I get stuck at the compiling of rts-base.p and here is my error > message. I included some previous lines since I get something weird with > rts-string.c (which is compiled two steps before the rts-base.p): > > error> rts-string.c:632: warning: no previous prototype for `_p_val_medcard_nocheck' > error> rts-string.c:633: warning: no previous prototype for `_p_val_longcard_nocheck' > error> rts-string.c:662: warning: no previous prototype for `_p_val_shortreal' > error> rts-string.c:663: warning: no previous prototype for `_p_val_real' > error> rts-string.c:664: warning: no previous prototype for `_p_val_longreal' Sorry, I can't help you with the real problem, but these warnings are normal. I wrote those functions and I was just too lazy to write prototypes for all of them. There are more warnings while compiling the RTS which can be ignored. Frank -- Frank Heckenbach, frank(a)pascal.gnu.de http://fjf.gnu.de/ PGP keys: http://pgp5.ai.mit.edu/pks/lookup?op=index&search=Frank+Heckenbach

1 0

GNU Pascal and Delphi
by Andreas Prucha [helicon] 27 Apr '98

27 Apr '98

Hi, I'm currently evaluating the possibility to use Linux for our applications in some cases. Our applications are written in OP (Delphi) and I've had a quick look at gpc and fpc. Well, the area where I imagine using Linux are server applications, and I hope to find a solution to use (widely) the same code-base for the NT-version and the Linux-version. Since these applications usually don't have a GUI, the visual part of the VCL is not the problem. And other parts can be easily ported. Anyway, I've read that GPC's focus is on portability. That's great. But I see no reason not to support the non-windows specific things. I know, OP is not based on a standard like Extended Pascal, /but/ I think OP /is/ the standard, because I can't imagine that any other Pascal-dialect is that widely used. Anyway, I've not check GPC very deeply, yet, so some of my statements might be wrong. Ok, here is what I'd like to see: - Compatibility with OP (Delphi) as far as possible w/o leaving the portabil ity-track. (Beside some features like message-handler-methods, there should not be much) - Exception handling - OP-style object-model - OP-style strings (reference-counted or not) However, IMO it is great, that Pascal is going to be supported in the UNIX-world. It is a under-estimated langugage (esp. OP), IMO. Andreas

2 1

Linking and Libraries...
by Orlando Llanes 26 Apr '98

26 Apr '98

I have 2 questions, I tried looking in the GPC and DJGPP docs but couldn't find it.. 1) Let's say I have a compiled routine with a .o extension, how can I link it with GPC in the same command-line? 2) How do I create a library? Thanks in advance! See ya! Orlando Llanes "Meine Damen und Herren, Elvis hat soeben das Gebaeude verlassen!" "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

2 1

Append()
by Mercator-Gymnasium 23 Apr '98

23 Apr '98

Is there an append() or similar procedure that allows me to write directly to the end of text files? If you have any information, please contact me direct by email. Thanks. Geoffrey Arnold garnold(a)cyberdrive.net Mercator-Gymnasium Duisburg Tel.: (0203) 283-7960 Fax: (0203) 283-7966

2 1

Re: trouble compiling gpc source on m68k
by Peter Gerwinski 23 Apr '98

23 Apr '98

Hi, Alan! > make[1]: Entering directory `/tmp/temp/gcc-2.8.0/p/rts' > ../../xgpc -B../../ --automake -c -DGPC -Wall -Wpointer-arith -Wmissing-prototy > pes -Wmissing-declarations -O3 -fomit-frame-pointer -I. -I../.. -I/tmp/temp/gcc > -2.8.0/p/rts/../.. -I/tmp/temp/gcc-2.8.0/p/rts/../../config rts-base.p > make[1]: *** [rts-base.o] IOT trap/Abort (core dumped) This *might* be a rather trivial problem with the version number. Please retry with a changed `p/version.c' that contains a line char *version_string = "2.8.0"; instead of char *version_string = GPC_VERSION_STRING; Good luck, Peter -- Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-980410 PGP: see homepage - 6C 94 45 BE 28 A4 96 - 0E CC E9 12 47 25 82 75 Fight the SPAM and UBE! - http://spam.abuse.net/ - http://maps.vix.com/

1 0

New Alpha gpc-980410 (source and binaries)
by Peter Gerwinski 22 Apr '98

22 Apr '98

Hello, everybody! A new alpha version, gpc-980410, is being uploaded to Agnes: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/ The major changes affect the DJGPP platform. Some crashes which occured under environments with memory protection (such as OS/2 or Windows 95) are fixed now. Some other minor fixes have been done, too (see `ChangeLog'). The problem was due to a new version of `libc.a' used in gpc-980405 which was necessary in order to fix the I/O problem in gpc-980401. The solution was to combine the old and the new version of `libc.a'. As you can imagine, compilation under DJGPP is now even harder than it was anyway ... The problem that `gpc' produces `.exe' files named `a.out' is still present. Just rename it, and it will work. :-/ Happy Eastern, :-) Peter

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

Gpc April 1998