July 2003 - Gpc

Get still an error under FreeBSD (for Mr. Heckenbach)
by Karim Forsthofer 27 Jul '03

27 Jul '03

Hello Sorry, for the delay.. I was in holiday. At the 15. of july, I wrote several Emails to the gpc mailing list, because I got same "make" error outputs, when I tried to compile gpc and gcc on my FreeBSD 5.1 OS. Frank Heckenback told me, to change a simple command in the ../gcc.3.2.1/gcc/intl/plural.y file. I changed it. But now , I get an other error msg from make (after running a long time). The last output is : gcc: No input files specified ***Error code 1 Stop in /usr/home/karim/gpc-build/gcc. etc. The msg is very short and I don`t know how to handle that or to fix it. Need some feedback Greetings __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Logos und KlingeltÃ¶ne fÃ¼rs Handy bei http://sms.yahoo.de

2 2

Re: overly aggressive warning message
by Joseph Oswald 27 Jul '03

27 Jul '03

Frank & Gale-- Thanks for your quick response to my e-mail. Most of the errors you refer to are well-localized in Knuth's source, and are part of the program that is meant to be modified to suit the particular platform that is being ported to. Once the WEB system is bootstrapped, each of the issues except for the for-loop one is a one-line change in the original source. At least in this respect, Knuth had the foresight to allow his programs to survive for what is a very long time in computer terms! Knuth was not programming in dec-pascal; as I recall it was in Pascal-H on the SAIL system. So I am not surprised that compiler directives have changed. However, on the for loop issue, I can see no practical advantage to enforcing this point of the standard to the point of not compiling the program. Can this aggressive behavior possibly be restricted to a --pedantic mode? I.e., can the error be demoted to a warning unless a --pedantic mode is enabled? On a larger scale, I think it is more useful for GPC to allow existing Pascal programs, with all their flaws, to be ported to GNU and other modern systems than for it to act as an enforcement mechanism to ensure that any Pascal programs that have harmless violations of the standard get weeded out. gcc as a whole takes a similar approach, I think. Thanks again to all the GPC contributors for an excellent tool! --Joe Oswald >I tried to compile Web and TeX and noticed a few more problems, >though apparently all quite minor: >- a lot of warnings which all seem to be harmless, but point to > unniceties in the code > >Time for `--dec-pascal' ...? > > > In > > the area of for-statements, there are latent errors in quite a few > > programs since there are quite a few compilers around which don't > > enforce all the for-statement requirements. > >Seems quite so. (GPC does one or two more now, but still not all.) _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail

2 1

BUG: GPC 20030507 on Mac OS X: does not recognize Macintosh line endings
by Joseph Oswald 27 Jul '03

27 Jul '03

The attached program and gzipped .txt files demonstrate a bug in GPC 20030507 compiled for Mac OS X. The EoLn(f) function does not recognize Macintosh line endings (character code decimal 13), only UNIX (decimal 10) line endings. Ideally, the EoLn behavior would recognize multiple possible line endings (including DOS CRLF), or at least be configurable at run-time. Running the macosx_eoln.pas on a Macintosh will result in the following output: file mac_eoln.txt had 0 lines. file unix_eoln.txt had 3 lines. Please be careful to preserve the line endings of the .txt.gz files in order to make the test a valid one. File transfer programs will often change the line endings of files believed to contain text, invalidating the test. gpc -v returns Reading specs from /Developer/Pascal/gpc33d6/lib/gcc-lib/powerpc-apple-darwin/3.3/specs Configured with: ../gpc-3.3d6/configure --enable-languages=pascal,c --enable-threads=posix --prefix=/Developer/Pascal/gpc33d6 --target=powerpc-apple-darwin Thread model: posix gpc version 20030507, based on gcc-3.3 Thank you for your help. --Joe oswald

1 0

Re: implicit object pointer dereference
by Adriaan van Os 26 Jul '03

26 Jul '03

Prof A Olowofoyeku (The African Chief) wrote: > What you are describing is almost equal to the "new" style Delphi > Classes (actually, this is already over 7 years old, so it is not so > new - but I use "new" here to distinguish it from the original BP > object model). That type of Delphi compatibility, is, I believe, on the > to-do list - but perhaps not a high priority. There is also the "Object-Oriented Extensions to Pascal" proposal, of the Technical Committee X3J9, see <http://www.pascal-central.com/OOE-stds.html>. In passing, I have to mention that I personally prefer the BP object model, see section "E.6.5.1 The Object Model. ... The reference model has the following disadvantages: ...". Still, it is a given fact that traditional Macintosh Pascal compilers implemented the reference model. Regards, Adriaan van Os

7 16

Line numbers in error msgs
by Paul Davidson 26 Jul '03

26 Jul '03

Looked at GPC and GCC command line options for ability to give line number (when applicable) of error in source code. Currently am seeing messages like: lists.pas:1: error: parse error before `:' Is there way to get the actual line number in code where the offending syntax lives? Thank you

3 5

Linking the libgpc to be shared
by "Nick Ioffe 25 Jul '03

25 Jul '03

Hi! I've tried to make my libgpc be shared. I work on HP SuperDome - hppa2.0w-hp-hpux11.00 (or at least the configure calls it so). I've tried to install gpc based on gcc-2.95.X unsuccesfully so I've installed gpc-20030509 based on gcc-3.2.1. Everything worked OK. But libgpc installed as static despite WITH_SHARED=yes option. After checking p/rts/Makefile I've pointed out that in that file WITH_SHARED= i.e. is just empty. After fixing it and making inside the rts I've got the following: nm: libgpc.so.2.1.20030509 not found. It was because of -Wl,-soname=libgpc.`cat ...` option specified to xgcc on the linking step. Eliminating it didn't help, now I got another error: LD: DP relative code in file /var/tmp/xxx.o - shared library ... Adding the -fPIC option used in building the *.lo files to linking command helped. Now the question - why configure doesn't do all these things? Also before that I got some strange errors when configure erroneusly created rts-config.h file - it didn't found open64 and usleep functions in /usr/local/include/fcntl.h - it was discovered by compiler. Any ideas, why? Thank you in advance, Nick

3 5

uninitialized Output
by "Nick Ioffe 24 Jul '03

24 Jul '03

Hi! I'm trying to run some pascal with java. After Markus Gerwinsky help and some hard work getting libgpc to be shared library it is possible. The problem that the first example I tried was printing something from Pascal with writeln. Then I got a runtime error that Output variable is uninitialized. Shouldn't gpc work with standard descriptors or the StdOut, StdErr and the rest should be initialized somehow? also how should I initialize them? To what device/descriptor etc? opening file and writing into it works. Nick

2 1

Shared libraries using GPC and JNI
by nick 23 Jul '03

23 Jul '03

Hi! I'm trying to use some old Pascal modules in Java through JNI. 1. Is there any way of using Pascal directly or should I use it through C? 2. How should I create the mixed shared library (i.e. library containing C and Pascal objects) 3. What version of GPC and GCC is it prefferable to use? Thank you in advance, Nick

3 3

-Wpacked
by Adriaan van Os 22 Jul '03

22 Jul '03

The warning argument -Wpacked issues the following warning while compiling any source (program or unit): [G4:~/gnu/testgpc/adriaan] adriaan% gpc hello.pas -Wpacked hello.pas:0: warning: packed attribute is unnecessary for `Datevalid' 'Datevalid' is the first field of the GPC internal variable GPC_TimeStamp (in p/rts/time.pas). It should be noted that -Wpacked issues warnings per field, not per record. This suggests that in the compiler back-end packing is a field-attribute, not a record attribute. This would also explain that "Datevalid' does not need a packed attribute (because it is the first field in the record) although GPC_TimeStamp is densely packed. I don't know whether this is target-platform dependent or not. Reading specs from /Developer/Pascal/gpc33d7/lib/gcc-lib/powerpc-apple-darwin/3.3/specs Configured with: ../gpc-3.3d7/configure --enable-languages=pascal,c --enable-threads=posix --prefix=/Developer/Pascal/gpc33d7 --target=powerpc-apple-darwin Thread model: posix gpc version 20030507, based on gcc-3.3 Regards, Adriaan van Os

1 0

CRT unit help
by Francisco Javier F. 22 Jul '03

22 Jul '03

I need to use the crt unit, but the compiler says that crt unit is not found: module/unit interface `Crt' could not be imported. Â¿Where is is supposed to be? thanx -- Now proudly running Debian Sid+ kernel 2.4.21 + XFS

2 1