Gpc June 1999

gpc@gnu.de

22 participants
50 discussions

help Newbi...`Gpc' could not be imported
by Oliver George 14 Jun '99

14 Jun '99

Hi, I installed gpc-19990118-1.i386-pc-linux-gnu.rpm and gpc-extras-19990118-1.i386-pc-linux-gnu.rpm and even recompiled from gpc-19990118-1.src.rpm and I am having the same troubles. Compiling a hello world works fine (only uses writeln) but compiler can't find GPC library... an example ------------ > gpc demoproc.pas demoproc.pas:25: module/unit interface `Gpc' could not be imported ------------ any suggestions, thanks Oliver.

2 1

Re: Huffman compression comes to GPC!
by Frank Heckenbach 13 Jun '99

13 Jun '99

"Dr A A Olowofoyeku" wrote: > I have just completed work on an Huffman compression unit which now > supports GPC. The unit exports two main (alternative) compression > functions and two decompression functions. The routines are "dead easy" > to use, and the compression ratio compares well with ZIP's "deflate". > > The file can be downloaded from the "contrib" directory on agnes: > ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/lhsix.zip One little comment: the characters you use in EncodeCallBack and DecodeCallBack are probably some graphics characters under Dos, but look a bit strange in the standard character set (a paragraph sign and an accented `u'). To avois this problem, it might be better to use ASCII characters (i.e., #32 .. #126), e.g. the hash (`#') that many programs use. I realise that this is only a demo program, but it gives a strange appearance at first sight... Frank -- Frank Heckenbach, frank(a)fjf.gnu.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

2 1

re: snapshot
by Russ Whitaker 12 Jun '99

12 Jun '99

oops: that's ar->/usr/bin/ar

1 0

Huffman compression comes to GPC!
by Dr A A Olowofoyeku 10 Jun '99

10 Jun '99

Hi folks! I have just completed work on an Huffman compression unit which now supports GPC. The unit exports two main (alternative) compression functions and two decompression functions. The routines are "dead easy" to use, and the compression ratio compares well with ZIP's "deflate". I have tried to make the code portable, and I believe that I have achieved this (it works fine with TP, BP, Delphi, FreePascal, and GPC). AFAIK there are no "endian" issues, but I stand corrected. Please report any bugs or portability problems to me. If you can fix any such problems, please send me a copy of the fix, so that I can merge it with the main distribution. The file can be downloaded from the "contrib" directory on agnes: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/lhsix.zip The unit deals with the compression of single files. Happy hacking! Best regards, The Chief -------- Dr. Abimbola A. Olowofoyeku (The African Chief) Email: laa12(a)keele.ac.uk Homepage: http://ourworld.compuserve.com/homepages/African_Chief/ Author of: Chief's Installer Pro v5.00 for Win32 ftp://ftp.simtel.net/pub/simtelnet/win95/install/chief500.zip

1 0

new snapshot
by Russ Whitaker 10 Jun '99

10 Jun '99

Hi peter downloaded the snapshot & cleaned out the old files here's the minor bugs ran into: 1. using CFLAGS="O2" the compile crashed in the same place as the previous snapshot: cc1 got fatal signal 6 [maths.o]Error1 while in the RTS subdirectory. compile ok without the CFLAGS 2. make looked for "ar" in wrong place: instead of /usr/bin looked at /usr/i586-pc-linux-gnu/bin/ar so put in a soft link to point to /usr/bin/ar and it worked 3. Didn't include --prefix=/usr/local so the install ended up in /usr/lib instead of /usr/local/lib moved i5* to /usr/local/lib/gcc* 4. either location gpc couldn't find the include files so moved /usr/local/lib/gcc*/i5*/2*/include/* to /usr/local/include and now works fine hope this helps thanks, Russ

1 0

Re: Unité crt.
by Frank Heckenbach 09 Jun '99

09 Jun '99

Olivier PECHEUX wrote: > Dimitri, tu dis :Ã§a marche. Chez Maurice, Ã§a marche. (unitÃ© crt). > > Chez moi, Ã§a ne marche que la premiÃ¨re fois. Ce que j'ai fait: > - j'ai chargÃ© le curse23.zip (indiquÃ© par Maurice). > - j'ai supprimÃ© le specs et le djgpp.djl > - j'ai modifiÃ© le djgpp.env (indiquÃ© par Olivier = moi) > _ j'ai tapÃ© le programme: > > program efface; > uses crt; > begin > clrscr; > readln > end. > > Quand je compile la premiÃ¨re fois, tout se passe bien, et le programme > fonctionne. > Si je compile une deuxiÃ¨me fois, je retrouve le messsage undefined > reference to crt_clrscr. Dans mon rÃ©pertoire de travail, j'ai les > fichiers gpc.o gpc.gpi crt.o crt.gpi et crtc.o . le fichier crtc.o > contient bien la procÃ©dure crt_clrscr (vue par nm -O crtc.o >crtc.lst). > Si je supprime lun des trois fichiers crt.gpi gpc.gpi ou crt.o , la > compilation fonctionne Ã nouveau. I must admit that I don't really speak French, but as far as I can understand, you can compile a program that uses CRT once succesfully, but not twice. Yes, this is a known problem with GPC's `automake' under DJGPP, and it affects all units, not just CRT. We'll try to fix it soon, but until then, you'll probably have to delete crt*.o before each compilation, or use the `--autobuild' switch. Both will force CRT to be recompiled, and then the problem does not appear. > Dans le fichier crtdummy.c (dans units), il est dit: > > - add a statement to #include that file, together with suitable #ifdefs > in crtc.c This statement only refers to those who want to port CRT to a new system (say, mingw). If you just want to use CRT under DJGPP, you don't need to worry about it. > The link to the last djgpp version of gpc in the directory > gnu-pascal/djgpp on agnes is not correct: > instead of > gpc20bb -> ../binary/gpc-19990530-i386-pc-djgppv202.zip > it should be > gpc20bb -> ../beta/binary/gpc-19990530-i386-pc-djgppv202.zip > > Quel est le nom exact complet? Dans > ftp://agnes.dida.physik.uni-essen.de/gnu-pascal je ne vois pas de djgpp. > le gpc20bb.zip que j'ai pris est tirÃ© de : > ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/current/binary/gpc-19990430-i386-pc-djgppv202.zip > . Ai-je pris le mauvais fichier? The `19990530' was a typo. 19990430 is the correct name of the last binary release for DJGPP. > To overwrite such a builtin specs, provide a new one in a rhide.env file > (either > the global one in %DJDIR%/share/rhide/ or a local one in the current > directory). > In you specific task you should place a line like the following: > > RHIDE_COMPILE_LINK_GPC_AUTOMAKE=$(RHIDE_LD_PASCAL) > $(RHIDE_LIBDIRS) -o $(OUTFILE) -automake $(RHIDE_GPC_FLAGS) > $(SOURCE_NAME) $(LIBRARIES) $(LDFLAGS) $(RHIDE_LDFLAGS) $(RHIDE_LIBS) > > (NOTE here, this should be all ONE long line!!!) > > > J'ai effectivement bien la spec indiquÃ©e. Je ne commprends pas bien ce > que je dois faire avec la fameuse ligne. Je l'ai mise seule dans un > fichier rhide.env mis dans les deux rÃ©pertoires indiquÃ©s sans aucun > changements. I'm not sure if I understand you correctly here, but if your problem is that there is no rhide.env file, then just create it in one of the directories mentioned, and put just this one line into it. I just tried it under Linux with the following line (note: the `$(LIBRARIES)' and `$(RHIDE_LIBS)' are also omitted because GPC cares about the libraries itself), and it seemed to work: RHIDE_COMPILE_LINK_PASCAL_AUTOMAKE=$(RHIDE_LD_PASCAL) $(RHIDE_LIBDIRS) $(RHIDE_LDFLAGS) -o $(OUTFILE) --automake $(RHIDE_GPC_FLAGS) $(SOURCE_NAME) $(RHIDE_LDFLAGS) Frank -- Frank Heckenbach, frank(a)fjf.gnu.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

2 2

Unité crt.
by Olivier PECHEUX 08 Jun '99

08 Jun '99

Dimitri, tu dis :Ã§a marche. Chez Maurice, Ã§a marche. (unitÃ© crt). Chez moi, Ã§a ne marche que la premiÃ¨re fois. Ce que j'ai fait: - j'ai chargÃ© le curse23.zip (indiquÃ© par Maurice). - j'ai supprimÃ© le specs et le djgpp.djl - j'ai modifiÃ© le djgpp.env (indiquÃ© par Olivier = moi) _ j'ai tapÃ© le programme: program efface; uses crt; begin clrscr; readln end. Quand je compile la premiÃ¨re fois, tout se passe bien, et le programme fonctionne. Si je compile une deuxiÃ¨me fois, je retrouve le messsage undefined reference to crt_clrscr. Dans mon rÃ©pertoire de travail, j'ai les fichiers gpc.o gpc.gpi crt.o crt.gpi et crtc.o . le fichier crtc.o contient bien la procÃ©dure crt_clrscr (vue par nm -O crtc.o >crtc.lst). Si je supprime lun des trois fichiers crt.gpi gpc.gpi ou crt.o , la compilation fonctionne Ã nouveau. Une idÃ©e? Merci. ----------------------------------------------------------------------- Dans le fichier crtdummy.c (dans units), il est dit: - add a statement to #include that file, together with suitable #ifdefs in crtc.c Alors la c'est la catastrophe! Qu'avez-vous compris? ------------------------------------------------------------------------ Maurice a Ã©crit: The link to the last djgpp version of gpc in the directory gnu-pascal/djgpp on agnes is not correct: instead of gpc20bb -> ../binary/gpc-19990530-i386-pc-djgppv202.zip it should be gpc20bb -> ../beta/binary/gpc-19990530-i386-pc-djgppv202.zip Quel est le nom exact complet? Dans ftp://agnes.dida.physik.uni-essen.de/gnu-pascal je ne vois pas de djgpp. le gpc20bb.zip que j'ai pris est tirÃ© de : ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/current/binary/gpc-19990430-i386-pc-djgppv202.zip . Ai-je pris le mauvais fichier? ------------------------------------------------------------------ Quand je compile avec rhide, j'ai un message "ignoring -g". J'ai contactÃ© Robert (auteur de rhide) qui m'a rÃ©pondu: To modify the calling sequences for external programs, you don't need to modify RHIDE itself. All is done via so called specs. You can see all the builtin specs by running redir -e specs rhide -E If you look at the file specs after this, you will find for instance a line like RHIDE_COMPILE_LINK_GPC_AUTOMAKE=$(RHIDE_LD_PASCAL) $(RHIDE_LIBDIRS) -o\ $(OUTFILE) --automake="$(strip $(RHIDE_GPC_FLAGS))"\ $(RHIDE_GPC_FLAGS) $(SOURCE_NAME) $(LIBRARIES) $(LDFLAGS)\ $(RHIDE_LDFLAGS) $(RHIDE_LIBS) To overwrite such a builtin specs, provide a new one in a rhide.env file (either the global one in %DJDIR%/share/rhide/ or a local one in the current directory). In you specific task you should place a line like the following: RHIDE_COMPILE_LINK_GPC_AUTOMAKE=$(RHIDE_LD_PASCAL) $(RHIDE_LIBDIRS) -o $(OUTFILE) -automake $(RHIDE_GPC_FLAGS) $(SOURCE_NAME) $(LIBRARIES) $(LDFLAGS) $(RHIDE_LDFLAGS) $(RHIDE_LIBS) (NOTE here, this should be all ONE long line!!!) J'ai effectivement bien la spec indiquÃ©e. Je ne commprends pas bien ce que je dois faire avec la fameuse ligne. Je l'ai mise seule dans un fichier rhide.env mis dans les deux rÃ©pertoires indiquÃ©s sans aucun changements. Heu... Au secours! --------------------------------------------------------------------- Ca fait quoi chez vous? A+ Olivier -- --------Publicite--personnelle--------------------------------------- ........ABC de la Programmation: ................http://www.multimania.com/opecheux Abonnez-vous aux listes francaises: - Assembleur: http://www.onelist.com/subscribe/prog_nasm - C : http://www.onelist.com/subscribe/prog_c_gnu - Pascal : http://www.onelist.com/subscribe/prog_pascal_gnu --

1 0

gpc-19990118 RPMs on Agnes
by Peter Gerwinski 04 Jun '99

04 Jun '99

Hello, the latest GPC beta gpc-19990118 is now available at `ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/' as RPM packages for the source and binaries (subdirectory `binary') for i386-pc-linux-gnu. Thanks to Jose Romildo Malaquias for building these packages. Peter -- Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-19990118 PGP key on request - 6C 94 45 BE 28 A4 96 - 0E CC E9 12 47 25 82 75 *** Vote against SPAM! ********* http://www.politik-digital.de/spam/ ***

1 0

Relationship between GPC and GCC on Linux (Compiling)
by Jose Romildo Malaquias 04 Jun '99

04 Jun '99

Hello. I am new to this list and to GPC. I have just downloaded latest GPC beta sources. I am going to build RPM packages from it (I was not able to find one) for RedHat Linux 6.0, which comes with EGCS 1.1.2 (egcs-2.91.66). 1. As there is not a patch for this version of EGCS in the GPC distribution, I decided to compile with the latest GCC (2.8.1). There is or will be patches for EGCS 1.1.2? 2. The compilation goes smoothly. Installation too. But should I keep the files /usr/lib/gcc-lib/i386-redhat-linux/2.8.1/{libgcc.a,spec} or they can be safely removed (and then GPC uses the ones from the EGCS installation)? Thanks. Prof. JosÃ© Romildo Malaquias <romildo(a)urano.iceb.ufop.br>

2 5

Incompatibility with gcc
by root 04 Jun '99

04 Jun '99

I install rh 6.0 that comes with the egcs-2.91.66 and my gpc 2.0 don't work now, and i don't know any site to dowload a pakage with gpc that work with this compiler. Can anybody help me, i need put the practics 9-6-99. please helpme.......

3 2

2025

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 June 1999