- Gpc - gnu.de

Re: Third Step
by Frank Heckenbach 28 Oct '99

28 Oct '99

I wrote: > Nicola Girardi wrote: > > > [...] Of course, my reply also shouldn't have gone to the list. Sorry. 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: Third Step
by Frank Heckenbach 27 Oct '99

27 Oct '99

Nicola Girardi wrote: > the editor is really what i was looking for, and i appreciate your work. Thanks. > i have something to say, anyway (i hope you'll find these as good > suggestions) > > 1) perhaps you should work on the syntax highlighting, i mean, you > should make both "BeGin" and "begin" highlighted, because pascal is > case insensitive Right. Will do so. (I always write my keywords in lower-case, so I didn't notice.) > 2) again for syntax hig. perhaps there should be a gray comment-highlight, > that doesn't seem to be present. No, it isn't there yet. As I said, the highlighting currently is a bit primitive. In particular, it only works per line. I have plans to do real highlighting, including multi-line comments, support for different languages and more, but it's not on the top of my priority list... So, what I could do now easily would be highlighting for comments within a single line, but I'm not sure if it's useful. What do you think? > 3) the date in the window title bar!! : > /home/girardi/typing/math3.pas 27.10.1999 > it is absolutely ugly :) You can turn the time and/or date off under Options/Environment/Clock, but for the next release, I've already changed the default to time only. > 4) some colors are a bit eye-breaking ;) You can change all the colors under Options/Colors, but if you tell me which ones you don't like and what you'd prefer, I might change the defaults. 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: Third Step
by Frank Heckenbach 27 Oct '99

27 Oct '99

Nicola Girardi wrote: > i worked it out :) > > [...] For those who wonder: This was a reply to a private mail, mistakenly posted to the list. If anyone has become curious about the editor, just stay tuned for a few days... ;-) 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

FreeBSD port
by Marc van Woerkom 27 Oct '99

27 Oct '99

Dear GNU Pascal developers, had another read of the GPC pages but I am still uncertain about your development model. At present I can spot source tarballs only and miss a CVS server badly. Is it possible to get access to the latest sources? It would help me considerably to arrange things with our folks responsible for the compiler. Regards, Marc

2 1

Re: Unit Printer
by Peter Gerwinski 27 Oct '99

27 Oct '99

Russ Whitaker wrote: > > 1) How do I pass '-Praw' to PrinterArguments? Like this: (Thanks, Frank!) program Foo; uses GPC, Printer; var Printer : Text; begin (* New (PrinterArguments, 1);*) getmem(printerarguments,8);{$w-}word(pointer(printerarguments)^):=1; PrinterArguments^[1] := NewString ('-Praw'); AssignPrinter (Printer, null); Rewrite (Printer); Writeln (Printer, 'foo') end. Unfortunately, there is a problem with schema types transported through units, so we need the workaround with `getmem'. I am currently working on this problem, so you will be able use the correct `New' in future releases of GPC. > 2) Any particular reason why PrinterArguments isn't just a string? When you are passing arguments to the program you already know their structure, so it's easy for you to decomposite them. If `PrinterArguments' were just a string, the `pipe' unit would have to do the decomposition before passing the parameters to the subprocess. Not a real problem, but it would be some unnecessary waste of resources. Hope this helps, Peter -- http://home.pages.de/~Peter.Gerwinski/ - G-N-U GmbH: http://www.g-n-u.de Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-19990118 GnuPG key fingerprint: 9E7C 0FC4 8A62 5536 1730 A932 9834 65DB 2143 9422 keys: ftp://ftp.gerwinski.de/pub/keys/ - AntiSpam: http://spam.abuse.net

1 0

Re: Installation problems?
by Peter Gerwinski 27 Oct '99

27 Oct '99

Jawaad Ahmad wrote: > Great! Thanx a lot...I was finally able to compile the simple Hello World > program. However, those GCC-related files take up 4 MB. Now they're taking > up 8 MB b/c they're in two different directories. I'm willing to live with > that, but there's gotta be a better way. If I install something that > assumes I have version 2.5, and another thing that wants version 2.0, will I > have to waste 12 MB? Anyway, thanx...the program compiles and runs! The next alpha snapshot of GPC will work with current versions of GCC, so this problem will vanish. > However, if I have a USES statement, e.g., USES Crt, or USES Gpc in the > sample PI.PAS program, I get the following message once again: > > > > [Win95] C:\TEMP\pas>gpc -Wall pi.pas > > pi.pas:35: warning: `{' within comment > > pi.pas:35: warning: `}' within comment > > pi.pas:26: module/unit interface `Gpc' could not be imported gpc -Wall --automake pi.pas Have fun, Peter PS: For such GPC-related questions of general interest, it's better to ask them on the GPC mailing list rather than to contact me personally. -- http://home.pages.de/~Peter.Gerwinski/ - G-N-U GmbH: http://www.g-n-u.de Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-19990118 GnuPG key fingerprint: 9E7C 0FC4 8A62 5536 1730 A932 9834 65DB 2143 9422 keys: ftp://ftp.gerwinski.de/pub/keys/ - AntiSpam: http://spam.abuse.net

2 2

gpc-19990813 with gcc-2.95 on solaris2.{6,7} and irix6.5 - anyone?
by Benedict Lofstedt 27 Oct '99

27 Oct '99

Hi, Has anyone out there managed to build gpc-19990813 with gcc-2.95 on solaris2.{6,7} and irix6.5 ? I have managed to get past a few hurdles: 1) gpc/p/config-lang.in uses test unknown on solaris [ -e $srcdir/p/Make-lang.in ] must be replaced by [ -r $srcdir/p/Make-lang.in ] --- gpc.orig/p/config-lang.in Tue Aug 3 00:18:13 1999 +++ gpc/p/config-lang.in Wed Oct 27 15:32:44 1999 @@ -43,10 +43,10 @@ echo "#define EGCS" > gcc-version.h echo "#define EGCS92" >> gcc-version.h echo "#define EGCS95" >> gcc-version.h - if [ -e $srcdir/p/Make-lang.in ] \ + if [ -r $srcdir/p/Make-lang.in ] \ && cmp -s $srcdir/p/Make-lang-2.95.in $srcdir/p/Make-lang.in; then true; else cp $srcdir/p/Make-lang-2.95.in $srcdir/p/Make-lang.in; fi - if [ -e $srcdir/p/Makefile.in ] \ + if [ -r $srcdir/p/Makefile.in ] \ && cmp -s $srcdir/p/Makefile-2.95.in $srcdir/p/Makefile.in; then true; else cp $srcdir/p/Makefile-2.95.in $srcdir/p/Makefile.in; fi else @@ -58,10 +58,10 @@ else echo "/* empty */" > gcc-version.h fi - if [ -e $srcdir/p/Make-lang.in ] \ + if [ -r $srcdir/p/Make-lang.in ] \ && cmp -s $srcdir/p/Make-lang-old.in $srcdir/p/Make-lang.in; then true; else cp $srcdir/p/Make-lang-old.in $srcdir/p/Make-lang.in; fi - if [ -e $srcdir/p/Makefile.in ] \ + if [ -r $srcdir/p/Makefile.in ] \ && cmp -s $srcdir/p/Makefile-old.in $srcdir/p/Makefile.in; then true; else cp $srcdir/p/Makefile-old.in $srcdir/p/Makefile.in; fi fi 2) gpc/p/gpc-decl.c needs declaration of nonlocal_goto_handler_slot --- gpc.orig/p/gpc-decl.c Wed Jul 28 03:31:23 1999 +++ gpc/p/gpc-decl.c Wed Oct 27 15:35:49 1999 @@ -54,6 +54,7 @@ #include <ctype.h> extern rtx tail_recursion_reentry; /* in function.c */ +extern rtx nonlocal_goto_handler_slot; /* in function.c */ /* for language specific parts of the tree_node */ extern struct obstack permanent_obstack; 3) An ugly hack to make two object files available [reported by Alexander Sokolov <robocop(a)amur.rosnet.ru> Fri, 20 Aug 1999 20:02:51 +1100 (VLAST) - if there was an answer, I missed it.] # An ugly hack ... rm -f gcc/choose-temp.o; ln -s ../libiberty/choose-temp.o gcc rm -f gcc/pexecute.o; ln -s ../libiberty/pexecute.o gcc 4) Comes to a grinding halt: The hacks&patches above get the build going, until gcc -c -DIN_GCC -DGPC -g -O2 -I. -I.. -I. -I./.. -I./../config -I./../.. /include gpc-lang.c gpc-lang.c: In function `lang_decode_option': gpc-lang.c:50: argument `p' doesn't match prototype ../tree.h:2078: prototype declaration gpc-lang.c:50: number of arguments doesn't match prototype ../tree.h:2078: prototype declaration where the symbol EGCS should be defined to get past this one, but if I do, then the next hurdle is: gcc -c -DIN_GCC -DGPC -DEGCS -I. -I.. -I. -I./.. -I./../config -I./../../include gpc-lex.c In file included from gpc-lex.c:41: gbe.h:79: conflicting types for `fatal' ../system.h:394: previous declaration of `fatal' In file included from gpc-lex.c:46: util.h:174: conflicting types for `concat' ../../include/libiberty.h:48: previous declaration of `concat' gpc-lex.c: In function `yyerror': gpc-lex.c:1158: argument `string' doesn't match prototype ../c-lex.h:84: prototype declaration gmake[2]: *** [gpc-lex.o] Error 1 Anyone with some help & advice out there? --- benedict

1 0

Re: Third Step
by Nicola Girardi 27 Oct '99

27 Oct '99

> > 2) i download the appropriate binary, and here's the result: > > ./peng: error in loading shared libraries > > : undefined symbol: __register_frame_info i worked it out :) the editor is really what i was looking for, and i appreciate your work. i have something to say, anyway (i hope you'll find these as good suggestions) 1) perhaps you should work on the syntax highlighting, i mean, you should make both "BeGin" and "begin" highlighted, because pascal is case insensitive 2) again for syntax hig. perhaps there should be a gray comment-highlight, that doesn't seem to be present. 3) the date in the window title bar!! : /home/girardi/typing/math3.pas 27.10.1999 it is absolutely ugly :) 4) some colors are a bit eye-breaking ;) anyway, i'm going to use it, you've been doing a good work -- Nicola Girardi girardi(at)keycomm.it Key fingerprint = CD 7D 57 C2 52 73 67 B5 13 48 AA 8C 3E 7F 13 DC

1 0

Re: Third Step
by Nicola Girardi 27 Oct '99

27 Oct '99

> > 1) why weren't there the sources ready to be compiled? > > I'm not releasing the sources yet, perhaps at some later time. > Currently, the sources are not in a shape that I want to release > them, sorry... oh, i was afraid u weren't going to release them at all :( > > 2) i download the appropriate binary, and here's the result: > > ./peng: error in loading shared libraries > > : undefined symbol: __register_frame_info > > This is a problem with glibc and programs compiled under SuSE Linux > (as PENG was) running under other distributions. Thanks for pointing > it out. > > Under http://sdb.suse.de/sdb/de/html/kukuk_regframe.html, they > provide a solution. Since the page seems to be available only in > German, I append below a translation made by the Alta Vista > translator (the language is a bit funny, but mostly readable ;-). > > The URL given is also wrong. The correct one is > ftp://ftp.suse.com/pub/suse_update/6.1/a1/regframe.rpm > > You can also wait a few days for the next release. I will link that > version statically to avoid such kinds of problems. i'll try to work it out. anyway, when the next release will be ready, i'll try it again. thanks, -- Nicola Girardi girardi(at)keycomm.it Key fingerprint = CD 7D 57 C2 52 73 67 B5 13 48 AA 8C 3E 7F 13 DC

1 0

Re: RHIDE problem
by Frank Heckenbach 25 Oct '99

25 Oct '99

Adam Naumowicz wrote: > Hello, > I know that probably it is not the best list to write about it, > but I know that most of GPC programmers use RHIDE, so I decided > to ask you. I use RHIDE on Linux successfully, but trying to install > it for my friend on RedHat 6.0 I encountered RTE at the first > attempt to start the editor. There was a message like 'segmentation fault, > unable to connect to a terminal' or something like that. Maybe it is a > known problem, maybe there is some work-around. My friend uses RIVA TNT > grafic card - maybe that is the problem ? Is the TERM variable set up correctly? Try `echo $TERM' in the shell -- it should say linux when on the console, or xterm, rxvt or something like that in an X terminal. If that's ok, it might be that rhide doesn't find the terminfo directories. Search for a file whose name is the TERM value in a directory whose name is only the first letter of that value below a directory like /usr/share/terminfo, /usr/lib/terminfo, /usr/local/share/terminfo /usr/local/lib/terminfo, e.g. /usr/lib/terminfo/l/linux. If you find it, set the main directory to the TERMINFO variable (`setenv TERMINFO /usr/lib/terminfo' in (t)csh; `export TERMINFO=/usr/lib/terminfo' in bash), or (as root) set a symlink to the directory where rhide expects it (I don't know which one, probably one of the above). If you don't find it at all, you might have to install the package containing terminfo (usually ncurses), though I can't imagine it hasn't been installed... 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