Gpc February 2000

gpc@gnu.de

29 participants
37 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

gpc mistake
by Jose Oliver Gil 29 Feb '00

29 Feb '00

Hello! I am using gpc version 970624(2.7.2.3) and I think there is something wrong. I have one Borland Pascal style unit, with the following text: def.p file: UNIT modul; INTERFACE TYPE CARDINAL = 0..65535; LONGBITSET = SET OF 0..63; IMPLEMENTATION END. and I use it in the following program as I show: test.p file: program test; USES modul; var i:CARDINAL; c:LONGBITSET; begin c:=[1]; i:=1; if (i in c) then writeln('yes'); end. I compile them (gpc -c def.p, gpc test.p) and the following error is displayed: gpc: Internal compiler error: program gpc1 got fatal signal 11 when everything should work fine! what's wrong? Thank you Jose Oliver Gil - mailto: joliver(a)gap.upv.es Grupo de Arquitecturas Paralelas - DISCA Universidad PolitÃ©cnica de Valencia - Spain UNIT modul; INTERFACE TYPE CARDINAL = 0..65535; LONGBITSET = SET OF 0..63; IMPLEMENTATION END. program test; USES modul; var i:CARDINAL; c:LONGBITSET; begin c:=[1]; i:=1; if (i in c) then writeln('yes'); end.

2 1

Re: faq - 2nd version
by Frank Heckenbach 29 Feb '00

29 Feb '00

Andreas Jaeger wrote: > I'm currently beta testing gpc for the next SuSE release. Since I'm > not really using gpc myself, could you help me what I should test, so > that SuSE 6.4 will have a working gpc? > > We're planning to use gpc 19991030 with gcc 2.95.2. > > I just did the following tests with some of the demos: > gromit:/usr/doc/packages/gpc/demos:[0]$ gpc --automake crtdemo.pas > gromit:/usr/doc/packages/gpc/demos:[0]$ ./a.out > > And the output looks fine. I think if this works, the installation is alright, and `make install' should be all that's required, but perhaps Peter can make a definitive statement. > I also run the test suite (installed in /usr/doc/packages/gpc/test) > and got only a few failures: > > TEST constovfl.pas: failed: failed: 0 > TEST fjf149.pas: Failed: 64 > TEST fjf83.pas: failed: Failed > /tmp/cc6RgcsV.s: Assembler messages: > /tmp/cc6RgcsV.s:115: Error: operands given don't match any known 386 instruction > TEST goto4.pas: failed > > > All other tests had an OK printed. I don't think that those failures > are serious, especially since I don't have libgmp installed on my system. Yes. AFAIK, libgmp is an optional package in SuSE, so you might want to specify it as a dependency... Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

1 0

Re: gpc
by Frank Heckenbach 29 Feb '00

29 Feb '00

Larry Poorman wrote: > I am using S.u.S.E 6.2 but wanted to try the Regular Expresions in > Pascal. So I de-installed the S.u.S.E version and downloaded a binary > and installed it. However when I enter: gpc -v > I get the following message: > > bash-2.03# gpc -v > GPC wrapper script, created by install-gpc-binary > Reading specs from > /usr/local/lib/gcc-lib/i586-pc-linux-gnulibc1/egcs-2.91.60/sp > gpc version 19990118, based on egcs-2.91.60 19981201 (egcs-1.1.1 > release) > ld -m elf_i386 -dynamic-linker /lib/ld-linux.so.1 /usr/lib/crt1.o > /usr/lib/crti > 6-pc-linux-gnulibc1/egcs-2.91.60/crtbegin.o -L > /usr/local/lib/gcc-lib/i586-pc-li > usr/local/lib/gcc-lib/i586-pc-linux-gnulibc1/egcs-2.91.60 > -L/usr/local/lib/gcc-l > s-2.91.60 -L/usr/local/lib -lgpc -lm -lgcc -lc -lgcc > /usr/local/lib/gcc-lib/i586 > 60/crtend.o /usr/lib/crtn.o > /usr/lib/crt1.o(.text+0x36): undefined reference to `main' > > Any suggestion as to what I could do to eliminate the "undefinded > reference to main" message? > > I have been using Borland Pascal for the last ten years (mostly > maintenance work as opposed to development) and therefore am curious as > to how GPC functions as compared to Borland, i.e. what are the TPU, TPP, > TPW equivalents in GPC and how are they linked in? If this is explained > in some part to the documentation just point me in that direction. Several things: - You use the install-gpc-binary script which is needed when installing a binary in a directory other than which it was compiled. This is not usually necessary under Linux (since we offer several binaries suited for different distributions and it's easy to compile GPC yourself under Linux), but it's not necessarily wrong... - The "undefined reference to `main'" problem when calling gpc with `-v' and some more parameters (which are implicitly passed by the install-gpc-binary script here) will be fixed in the next release, but it's not very serious, anyway. As soon as you actually compile a program (i.e., give a file name), it does not occur. - The equivalent of BP's tp[upw] files in GPC are object files (.o) plus interface files (.gpi) (and in the case of EP modules rather than BP units, also .gpm files). The object files are completely compatible with GCC and (at least under Unix systems) just about any other compiler and assembler, so they are linked with the default linker (ld) which is called automatically by GPC when compiling a program. (OTOH, if you just want to compile a unit alone, and not link it, you have to give the `-c' switch.) The .gpi and .gpm files are used by GPC only and are read when compiling a program, unit or module that uses another unit or module. - When compiling a program that uses units, give the `--automake' switch to make GPC compile the units automatically. - For regular expressions you need the rx library. If it isn't installed on your system, you can get it from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/libs/ Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

1 0

Re: faq - 2nd version
by Andreas Jaeger 29 Feb '00

29 Feb '00

>>>>> Frank Heckenbach writes: Frank> Khimenko Victor wrote: >> 23-Feb-00 15:45 you wrote: >> > Khimenko Victor wrote: >> >> > please mention this is not necessary for Debian GNU/Linux and >> >> > Debian GNU/Hurd. The current gpc can be fetched from www.debian.org >> >> > for the architectures alpha, arm, i386, m68k, sparc and powerpc. >> >> >> >> This is true for KSI-Linux & SuSE as well AFAIK. So IMO to write something >> >> "if you are plan to use version of GPC not included in your distribution then >> >> vetter to build GPC yourself because..." >> >> > Nope. The GPC distribution that comes with SuSE-6.3 is >> > misinstalled. It does not find the standard units (such as >> > CRT). I am getting complaints from users about this regularly. >> >> Hmm. Looks like two-ended sword to me :-) SuSE-6.3 DOES NOT install CRT. >> But 'make install' does not install CRT as well (AFAIK). So I'm not sure if >> only SuSE must be blamed here... >> >> P.S. I mean 'does not install CRT in usable state' of course. You can not just >> 'use CRT;' fire gpc and get working program after `make install'... Frank> Yes, you can if you compile with `--automake' (and have ncurses Frank> installed which shouldn't be a problem under Linux). Frank> The CRT unit (as well as the other units) are installed in source Frank> form which I think is fine for a free compiler, and will be compiled Frank> when needed (using `--automake') with your favourite options Frank> (optimization, debugging, etc.). The problem with SuSE, AFAIUI Frank> (can't check myself) is that either the unit sources are not Frank> installed, or there is some path problem so the installed GPC does Frank> not find them. I'm currently beta testing gpc for the next SuSE release. Since I'm not really using gpc myself, could you help me what I should test, so that SuSE 6.4 will have a working gpc? We're planning to use gpc 19991030 with gcc 2.95.2. I just did the following tests with some of the demos: gromit:/usr/doc/packages/gpc/demos:[0]$ gpc --automake crtdemo.pas gromit:/usr/doc/packages/gpc/demos:[0]$ ./a.out And the output looks fine. I also run the test suite (installed in /usr/doc/packages/gpc/test) and got only a few failures: TEST constovfl.pas: failed: failed: 0 /usr/bin/ld: cannot open -lgmp: Datei oder Verzeichnis nicht gefunden collect2: ld returned 1 exit status TEST dialec3.pas: failed TEST dialec4.pas: OK /usr/bin/ld: cannot open -lgmp: Datei oder Verzeichnis nicht gefunden collect2: ld returned 1 exit status TEST dialec5.pas: failed /usr/bin/ld: cannot open -lgmp: Datei oder Verzeichnis nicht gefunden collect2: ld returned 1 exit status TEST dialec6.pas: failed TEST fjf149.pas: Failed: 64 TEST fjf83.pas: failed: Failed /tmp/cc6RgcsV.s: Assembler messages: /tmp/cc6RgcsV.s:115: Error: operands given don't match any known 386 instruction TEST goto4.pas: failed All other tests had an OK printed. I don't think that those failures are serious, especially since I don't have libgmp installed on my system. Looking over the discussion again, Khimenko mentioned: > Hmm. Looks like two-ended sword to me :-) SuSE-6.3 DOES NOT install CRT. > But 'make install' does not install CRT as well (AFAIK). So I'm not sure if > only SuSE must be blamed here... > > P.S. I mean 'does not install CRT in usable state' of course. You can not just > 'use CRT;' fire gpc and get working program after `make install'... Is there any other command (beside 'make install'[1]) that should be issued? I'm now checking the sources myself Btw. I double checked that the units are installed: /usr/lib/gcc-lib/i386-suse-linux/2.95.2/units /usr/lib/gcc-lib/i386-suse-linux/2.95.2/units/crt.inc /usr/lib/gcc-lib/i386-suse-linux/2.95.2/units/crt.pas /usr/lib/gcc-lib/i386-suse-linux/2.95.2/units/crtc.c /usr/lib/gcc-lib/i386-suse-linux/2.95.2/units/crtc.h [...] Thanks for your help and a great work! Andreas Footnotes: [1] I didn't found anything while RTFMing. -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.rhein-neckar.de

1 0

gpc
by Larry Poorman 28 Feb '00

28 Feb '00

Hello, I am using S.u.S.E 6.2 but wanted to try the Regular Expresions in Pascal. So I de-installed the S.u.S.E version and downloaded a binary and installed it. However when I enter: gpc -v I get the following message: bash-2.03# gpc -v GPC wrapper script, created by install-gpc-binary Reading specs from /usr/local/lib/gcc-lib/i586-pc-linux-gnulibc1/egcs-2.91.60/sp gpc version 19990118, based on egcs-2.91.60 19981201 (egcs-1.1.1 release) ld -m elf_i386 -dynamic-linker /lib/ld-linux.so.1 /usr/lib/crt1.o /usr/lib/crti 6-pc-linux-gnulibc1/egcs-2.91.60/crtbegin.o -L /usr/local/lib/gcc-lib/i586-pc-li usr/local/lib/gcc-lib/i586-pc-linux-gnulibc1/egcs-2.91.60 -L/usr/local/lib/gcc-l s-2.91.60 -L/usr/local/lib -lgpc -lm -lgcc -lc -lgcc /usr/local/lib/gcc-lib/i586 60/crtend.o /usr/lib/crtn.o /usr/lib/crt1.o(.text+0x36): undefined reference to `main' Any suggestion as to what I could do to eliminate the "undefinded reference to main" message? I have been using Borland Pascal for the last ten years (mostly maintenance work as opposed to development) and therefore am curious as to how GPC functions as compared to Borland, i.e. what are the TPU, TPP, TPW equivalents in GPC and how are they linked in? If this is explained in some part to the documentation just point me in that direction. mfG, Larry

1 0

Svgalib-GPC-20000216 - Graphics library for GPC
by Nicola Girardi 26 Feb '00

26 Feb '00

Svgalib-GPC is a set of graphics units for GNU-Pascal. The units are the rewriting of data contained in the header include files included in the Svgalib distribution, in a manner which make it easy for Pascal programmers to use Svgalib without needing to rewrite prototypes. Most units just contain the prototypes for using Svgalib functions, with some adjustments regarding Boolean return values and CString stuff. The keyboard units (raw and normal mode) yet are rewritten using TFDD capabilities (and thanks to Frank for the explanation) and they seem to work well. I think the package is alright but I haven't tested it out much. So current status is neither of alpha, beta, gamma, delta, YOU have to tell me :-) The full library is distributed under the GNU LGPL. For details read the file COPYING.LIB contained in the tarball. Svgalib-GPC needs the latest alpha version of GPC, because of the TFDD stuff, and it's not that portable, in fact I think it's useable for Linux/x86 only, but it might work under other systems with svgalib4ggi. If you're going to test it for me, please tell me about the results. There are not good demos in the tarball to show you the capabilities of this all, and I'm not spending much time coding new features or demos. I think I'll improve this just if I get feedback and requests :-) Just because I enjoy only if people use what I code :-) If you have to report bugs, suggestions, requests, write to me at this address girardi(a)keycomm.it The site where you can find a bit more details about the units and download the current tarball is: http://agnes.dida.physik.uni-essen.de/~nicola/ Thanks to: Frank Heckenbach for help with TFDD stuff and for getting me to release this and Peter Gerwinski for the account on agnes. Have fun :) -- Nicola Girardi <girardi(a)keycomm.it> Key fingerprint = 5D9E ED36 C2E9 EF8F C4B6 25C2 3FF4 E5A2 27A7 83B9 GnuPG Key at http://agnes.dida.physik.uni-essen.de/~nicola/gpg-plan

1 0

Re: faq - 2nd version
by Frank Heckenbach 24 Feb '00

24 Feb '00

Khimenko Victor wrote: > 23-Feb-00 15:45 you wrote: > > Khimenko Victor wrote: > >> > please mention this is not necessary for Debian GNU/Linux and > >> > Debian GNU/Hurd. The current gpc can be fetched from www.debian.org > >> > for the architectures alpha, arm, i386, m68k, sparc and powerpc. > >> > >> This is true for KSI-Linux & SuSE as well AFAIK. So IMO to write something > >> "if you are plan to use version of GPC not included in your distribution then > >> vetter to build GPC yourself because..." > > > Nope. The GPC distribution that comes with SuSE-6.3 is > > misinstalled. It does not find the standard units (such as > > CRT). I am getting complaints from users about this regularly. > > Hmm. Looks like two-ended sword to me :-) SuSE-6.3 DOES NOT install CRT. > But 'make install' does not install CRT as well (AFAIK). So I'm not sure if > only SuSE must be blamed here... > > P.S. I mean 'does not install CRT in usable state' of course. You can not just > 'use CRT;' fire gpc and get working program after `make install'... Yes, you can if you compile with `--automake' (and have ncurses installed which shouldn't be a problem under Linux). The CRT unit (as well as the other units) are installed in source form which I think is fine for a free compiler, and will be compiled when needed (using `--automake') with your favourite options (optimization, debugging, etc.). The problem with SuSE, AFAIUI (can't check myself) is that either the unit sources are not installed, or there is some path problem so the installed GPC does not find them. Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

1 0

Re: faq - 2nd version
by Frank Heckenbach 24 Feb '00

24 Feb '00

I found the following request on Usenet: : From: "Rodrigo de Salvo Braz" <Rodrigo_Braz(a)brown.edu.nospam> : Newsgroups: comp.lang.pascal.misc : Subject: *Overview* documentation for GNU Pascal?!? : Date: Mon, 14 Feb 2000 11:49:26 -0500 : Organization: Brown University : Lines: 14 : Message-ID: <889bj7$ks5(a)cocoa.brown.edu> : NNTP-Posting-Host: 128.148.208.188 : : Hi, : : I have been trying to use GNU Pascal but found surprinsingly hard to find : instructions on the most basic things. Everywhere it seems to be assumed : that I know what libraries to use, what kind of file I want to generate. All : I get is detailed descriptions of options that do things I don't know about. : : So, does anyone know where to get overview documentation? : : Thanks, : : Rodrigo Since this seems to be a typical problem, i.e., getting started seems to be the most difficult thing about GPC, I suggest to write more about this in the FAQ, as detailed as possibled -- starting from zero, covering different platforms, when (and how) to get a GPC binary or rather the source distribution, etc. E.g., on Linux you better build GPC yourself because of glibc incompatibilities, but you can assume gcc, binutils, libc, ncurses etc. to be present, while under Dos, you better get a GPC binary for the first try and you need other files (that's already in the FAQ). The Chief is just writing a FAQ about building under MS-Windows which could be included or referenced. Another thing to mention is the libraries needed by some Pascal units, see ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/libs/README (you can copy the text if you want). This is to say that it would be good to have the most important information for starters (what, where, how) available in one place. Perhaps it's also a good idea to copy some (not all!) information useful for starters from the GPC web pages. Then, of course, you might want to answer the request in the newsgroup with a pointer to the FAQ... :-) Frank -- Frank Heckenbach, frank(a)g-n-u.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

4 4

RE: faq - 2nd version - gpc binaries dos
by Klaus Friis Østergaard 21 Feb '00

21 Feb '00

.... Since this seems to be a typical problem, i.e., getting started seems to be the most difficult thing about GPC, I suggest to write more about this in the FAQ, as detailed as possibled -- starting from zero, covering different platforms, when (and how) to get a GPC binary or rather the source distribution, etc. E.g., on Linux you better build GPC yourself because of glibc incompatibilities, but you can assume gcc, binutils, libc, ncurses etc. to be present, while under Dos, you better get a GPC binary for the first try and you need other files (that's already in the FAQ). The Chief is just writing a FAQ about building under MS-Windows which could be included or referenced. Another thing to mention is the libraries needed by some Pascal units, see ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/libs/README (you can copy the text if you want). ...... Frank With the binary distribution of gpc for djgpp - what is the problem with archieving all that is need in one file. I think this would help alot, also avoids problems with mismatch between the gpb binary and the compiler version of the C compiler.

1 0

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 February 2000