Gpc May 2002

gpc@gnu.de

19 participants
28 discussions

gpcbuild - still failing
by toms＠ncifcrf.gov 17 May '02

17 May '02

Joe: > Well, perhaps there was a problem because you elected to use > a different directory to the default (ie. /usr/local)? OTOH, I would > expect that one of the steps should have stopped with an error > message, if there was a problem? Thanks. No errors to indicate that. OTOH there is so much stuff going by on the screen - how is one to know if a warning is a problem? I get ../../gcc-2.95.2/gcc/toplev.c:1178: warning: initialization from incompatible po is that a problem? > I was able to compile without problems by following the instructions > verbatim (except that I chose "/temp/build" rather than "/home/fred" > as the working directory and GCC 2.95.3 instead of 2.95.1). So, it > does work and the instructions are correct. I have Mandrake 8.0 > and build GPC based on the SuSE GCC source code (I was logged > as "root", so I didn't need to worry about write privileges). > > BTW, shouldn't "gpc-20020410" be "gpc-20020510", instead? I wish. I modified the code of gpcbuild so it would not make a mistake like that again. The problem was that, unfortunately, the directory inside package.tar.gz is NOT 'package'; that was a pain until I realized I could use tar tzf to get the current name. (The intent of gpcbuild is that it can just figure out all the names by itself. If there is an upgrade, I'll just run it again and get a complete build next time with one command. Only ... it doesn't work yet! :-) So it now seems to run just fine, doing all the steps. There is a cryptic statement at http://www.gnu-pascal.de/gpc_51.html#SEC51 to 'Make sure that GNU make is installed.' A clue as to how to check that would be useful!!! Please add something there in the manual, thanks. To be safe I switched to gmake but it made no difference. Does my script work on other systems? (It gives lots of errors on the c compile on solaris ... don't these scripts detect their environment?) Tom Dr. Thomas D. Schneider National Cancer Institute Laboratory of Experimental and Computational Biology Frederick, Maryland 21702-1201 toms(a)ncifcrf.gov permanent email: toms(a)alum.mit.edu http://www.lecb.ncifcrf.gov/~toms/

2 1

Can't compile GPC for FreeBSD 4
by Michael Kochiashvili 16 May '02

16 May '02

Hello, trying compile GPC for FreeBsd... Have download packages from your page gpc-2.1.tar.gz gcc-core-2.95.2.tar.gz Have perform steps 2,3 (Unpacking the source, Configuring and building GCC) as described at http://www.gnu-pascal.de/gpc_51.html#SEC51 When make step 5 Compiling GPC I get this error =================================================================== ... src=`cd /usr/local/mine_sources/gcc-2.95.2/gcc && pwd` && cd /usr/local/mine_sources/gcc-2.95.2/gcc/p/rts && make -f Makefile.in srcdir=. SCRIPTDIR="$src/p/script" SHELL="/bin/sh" CFLAGS="-g -O2" AR="ar" AR_FLAGS="rc" RANLIB="ranlib" RANLIB_TEST="[ -f ranlib ] || ( [ "i386-unknown-freebsdelf" = "i386-unknown-freebsdelf" ] && [ -f /usr/bin/ranlib -o -f /bin/ranlib ] )" RTSFLAGS="" DESTDIR="../.." generated-files src=`cd /usr/local/mine_sources/gcc-2.95.2/gcc && pwd` && cd /usr/local/mine_sources/gcc-2.95.2/gcc/p/rts && make -f Makefile.in srcdir=. SCRIPTDIR="$src/p/script" SHELL="/bin/sh" CFLAGS="-g -O2" AR="ar" AR_FLAGS="rc" RANLIB="ranlib" RANLIB_TEST="[ -f ranlib ] || ( [ "i386-unknown-freebsdelf" = "i386-unknown-freebsdelf" ] && [ -f /usr/bin/ranlib -o -f /bin/ranlib ] )" RTSFLAGS="" DESTDIR="../.." generated-files /usr/local/mine_sources/gcc-2.95.2/gcc/p/script/mkdir-p p/rts src=`cd /usr/local/mine_sources/gcc-2.95.2/gcc && pwd` && cd p/rts && CC="`echo /usr/local/mine_sources/gpc-build/gcc/xgcc -B/usr/local/mine_sources/gpc-build/gcc/ -B/usr/local/i386-unknown-freebsdelf/bin/ -I/usr/local/i386-unknown-freebsdelf/include' ' | sed -e 's,-B$[^/][^:]$,-B../../\1,g;s,^$[^/][^:]$,../../\1,'`" PC="`echo ./xgpc -B./' ' | sed -e 's,-B$[^/][^:]$,-B../../\1,g;s,^$[^/][^:]$,../../\1,'`" CONFIG_SITE=nonexisting-file $src/p/rts/configure --silent > /dev/null --srcdir=$src/p/rts `if [ x@with_shared@ = xyes ]; then echo '--with-shared'; fi` src=`cd /usr/local/mine_sources/gcc-2.95.2/gcc && pwd` && cd p/rts && make CC="`echo /usr/local/mine_sources/gpc-build/gcc/xgcc -B/usr/local/mine_sources/gpc-build/gcc/ -B/usr/local/i386-unknown-freebsdelf/bin/ -I/usr/local/i386-unknown-freebsdelf/include' ' | sed -e 's,-B$[^/][^:]$,-B../../\1,g;s,^$[^/][^:]$,../../\1,'`" PC="`echo ./xgpc -B./' ' | sed -e 's,-B$[^/][^:]$,-B../../\1,g;s,^$[^/][^:]$,../../\1,'`" SCRIPTDIR="$src/p/script" SHELL="/bin/sh" CFLAGS="-g -O2" AR="ar" AR_FLAGS="rc" RANLIB="ranlib" RANLIB_TEST="[ -f ranlib ] || ( [ "i386-unknown-freebsdelf" = "i386-unknown-freebsdelf" ] && [ -f /usr/bin/ranlib -o -f /bin/ranlib ] )" RTSFLAGS="" DESTDIR="../.." all ../.././xgpc -B../.././ -I. -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -g -O2 -DRTS_RELEASE_STRING="'`cat /usr/local/mine_sources/gcc-2.95.2/gcc/p/rts/rts-version`'" --unit-path=/usr/local/mine_sources/gcc-2.95.2/gcc/p/rts --automake --print-needed-options "" 2> "needed-options" || true if grep -v '^--' "needed-options" > /dev/null; then echo "needed-options: `cat "needed-options"`"; rm -f "needed-options"; false; else true; fi needed-options: xgpc: : No such file or directory xgpc: No input files *** Error code 1 Stop in /usr/local/mine_sources/gpc-build/gcc/p/rts. *** Error code 1 Stop in /usr/local/mine_sources/gpc-build/gcc. *** Error code 1 Stop in /usr/local/mine_sources/gpc-build. =================================================================== Can you help me with any suggestion? Thank you -- Michael Kochiashvili http://www.iberiapac.ge/~kochini/

2 1

Re: almost there?
by da Silva, Joe 16 May '02

16 May '02

Well, perhaps there was a problem because you elected to use a different directory to the default (ie. /usr/local)? OTOH, I would expect that one of the steps should have stopped with an error message, if there was a problem? I was able to compile without problems by following the instructions verbatim (except that I chose "/temp/build" rather than "/home/fred" as the working directory and GCC 2.95.3 instead of 2.95.1). So, it does work and the instructions are correct. I have Mandrake 8.0 and build GPC based on the SuSE GCC source code (I was logged as "root", so I didn't need to worry about write privileges). BTW, shouldn't "gpc-20020410" be "gpc-20020510", instead? Joe. > -----Original Message----- > From: toms(a)ncifcrf.gov [SMTP:toms@ncifcrf.gov] > Sent: Thursday, May 16, 2002 3:57 PM > To: gpc(a)gnu.de; tds(a)fred.net > Subject: almost there? > > Folks: > > I seem to have done most everything to compile, but > > have nothing in my bin directory: > > /users/tds/now/gpc/current>ls > bin/ info/ > i386-unknown-freebsdelf/ lib/ > include/ man/ > /users/tds/now/gpc/current>ls bin > cpp* i386-unknown-freebsdelf-gcc* > gcc* protoize* > gcov* unprotoize* > > Any clues about where the binary went?? > > I didn't find this process simple at all. I'm building a script to do the > entire job automatically, because this process is pretty complicated to > repeat by hand each time: > > http://www.fred.net/tds/gpcbuild > > What's wrong with it? > > Tom > > Dr. Thomas D. Schneider > National Cancer Institute > Laboratory of Experimental and Computational Biology > Frederick, Maryland 21702-1201 > toms(a)ncifcrf.gov > permanent email: toms(a)alum.mit.edu > http://www.lecb.ncifcrf.gov/~toms/

1 0

almost there?
by toms＠ncifcrf.gov 16 May '02

16 May '02

Folks: I seem to have done most everything to compile, but have nothing in my bin directory: /users/tds/now/gpc/current>ls bin/ info/ i386-unknown-freebsdelf/ lib/ include/ man/ /users/tds/now/gpc/current>ls bin cpp* i386-unknown-freebsdelf-gcc* gcc* protoize* gcov* unprotoize* Any clues about where the binary went?? I didn't find this process simple at all. I'm building a script to do the entire job automatically, because this process is pretty complicated to repeat by hand each time: http://www.fred.net/tds/gpcbuild What's wrong with it? Tom Dr. Thomas D. Schneider National Cancer Institute Laboratory of Experimental and Computational Biology Frederick, Maryland 21702-1201 toms(a)ncifcrf.gov permanent email: toms(a)alum.mit.edu http://www.lecb.ncifcrf.gov/~toms/

1 0

compiler warning on shortCard
by Toby Ewing 15 May '02

15 May '02

Hi, all Having fun with Schema; thanks, Frank! I mentioned yesterday that I was getting a compiler warning when I used Cards rather than Integers for Schema, and Frank wanted to know more. Below is a (remarkably familiar) test program. When I compile the program, I get the warning: Warning: comparison is always "True" due to limited range of data type for the three "i" loops. Oddly enough, the "j" and "k" loops get no warning, though in other similar programs I've had warnings for each of nested loops. The medCard variables do not produce warnings when changed to shortCard, nor does the shortCard variable produce an error if it is changed to medCard. As you might guess, byteCard produces the same warning as shortCard. regards, Toby ----------------------------------- program testmem; type Fieldary(sY, sZ : medCard) = array[1..sY,1..sZ] of Real; FPary(sX : medCard) = array[0..sX] of ^Fieldary; var Field : ^FPary; i, j, k : byteCard; nx, ny, nz : medCard; begin write('Enter sizes in x, y, and z: '); readln(nx, ny, nz); New(Field, nx); for i := 0 to nx do New(Field^[i], ny, nz); writeln('Memory allocated OK'); for i := 0 to nx do for j := 1 to nx do for k := 1 to nx do Field^[i]^[j,k] := 1.0 * i * j * k; writeln('Freeing memory...'); for i := 0 to nx do Dispose(Field^[i]); Dispose(Field); end.

3 3

Record Field Alignment
by KOCHERALKOTA harikrishna 15 May '02

15 May '02

Hello, Is there any way in GPC for doing record field alignment to a byte which is default in Borland Pascal.? One more Clarification on the line given below which is taken from the GPC documetation? gpc.info-1(297): - True packed records and arrays. Pack 8 Booleans into 1 byte. I understood that GPC Does true packing on records and arrays. And i also tried the sample program (packingdemo.pas) given by gpc. see the declaration below var A: packed array [1 ..7] of Boolean; The size of A is expected to be 1 byte but it is 2 bytes. For values 9..16 the size is 2 bytes which is ok. once again for values 17...24 it gives 4 bytes(3 bytes expected). why it is so? Thanks and Regards Karthic And Harikrishna

1 0

accessing packed record fields
by KOCHERALKOTA harikrishna 14 May '02

14 May '02

Hello, When accessing the address of a field in a Packed record, it gives an compilation error(platform is solaris 2.6). The error says "cannot take address of bitfield <field name>". Is that true in gpc that one cannot take the address of a field in a packed record ? Is there any other way of solving it? Thanks and Regards, Harikrishna

3 2

Re: GPC 2.1 released
by da Silva, Joe 14 May '02

14 May '02

Yes, that's much better! :-) Joe. > -----Original Message----- > From: Frank Heckenbach [SMTP:frank@g-n-u.de] > Sent: Tuesday, May 14, 2002 5:14 AM > To: gpc(a)gnu.de > Subject: Re: GPC 2.1 released > > da Silva, Joe wrote: > > > Congratulations! Fantastic work!!! > > Thanks. :-) > > > I have one or two suggestions/queries regarding the web page > > "http://www.gnu-pascal.de/download.html" however ... > > > > Firstly, it states that the "http://www.gnu-pascal.de/current/" web > > page is a development snapshot, to be used "at your own risk". > > Is this correct? Isn't that what the "Alpha" and "Beta" directories > > are for? > > Whoops. I expected that some stupid bug would be left, but I'm glad > that it's only on the website (at least until now ;-). > > Fixed. > > > Secondly, it would be helpful to new visitors if the "download" > > page also included a link to "http://www.gnu-pascal.de/binary/". > > After all, new visitors are much more likely to want to download > > a binary than the source code, so this should be presented to > > them directly on the "download" page (also, they could easily > > overlook the "Binary" link at the top of the "Current" web page). > > OK. > > > Finally, it would also be helpful to new visitors if the notes at > > the bottom of the "Libraries" section of the "download" page, > > included a short (one sentence) description of what these > > libraries actually are. It's all rather cryptic otherwise. > > I've made a link to the libraries page. > > Better now? > > Frank > > -- > Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/, 7977168E > GPC To-Do list, latest features, fixed bugs: > http://www.gnu-pascal.de/todo.html

1 0

new coompiler, old problem?
by Toby Ewing 14 May '02

14 May '02

Hi, all I have encountered a bug in the old compiler. See test program below. I thought perhaps this had been fixed in version 2.1, but when I installed 2.1, I couldn't get it to compile! I get the message djgpp.ver: No such file or directory (ENOENT) I expect this is a simple fix. What am I missing? FYI, I installed the new gpc files into a new directory, then (because it uses gcc 2.95.3 rather than the new 3.0.0) I put my old 2.95.3 files into the new djgpp directory structure, being careful not to overwrite any new gpc files. I'm running on an Athlon usder win98, and have used gpc for about 5 years. The problem in the old compiler is a crash when writing. The reason for the program approach is this: I'm trying to distribute a program where the user specifies a matrix size in the input file, so I can distribute a binary and users don't need to have a compiler in order to resize the matrix. I've worked with this memory model before, and it worked fine. But now I'm having trouble, and I don't see the problem. many thanks for the old and new compilers, which make my work possible. Toby ------------------------------- program testmem; const Xmax = 25; type Fieldary = array[1..2] of real; FPary = array[0..Xmax] of ^Fieldary; var Field : FPary; FSize, i,j, k, nx : integer; begin writeln; write('Enter the size: '); {I used 5} readln(nx); FSize := 8 * sqr(nx); {making a cube. *8 is for "real"} for i := 0 to nx do GetMem(Field[i], FSize); writeln('Memory allocated OK'); for i := 0 to nx do for j := 1 to nx do for k := 1 to nx do Field[i]^[j+(nx*k)] := 1.0 * i * j * k; writeln('Done assigning. Writing...'); for i := 0 to nx do for j := 1 to nx do begin for k := 1 to nx do write(Field[i]^[j+(nx*k)]:8:1, ' '); {<== CRASHES HERE with a GPF} writeln; end; writeln('Freeing memory...'); for i := 0 to nx do if (Field[i] <> Nil) then FreeMem(Field[i]); end.

3 6

Re: GPC 2.1 released
by da Silva, Joe 13 May '02

13 May '02

Congratulations! Fantastic work!!! I have one or two suggestions/queries regarding the web page "http://www.gnu-pascal.de/download.html" however ... Firstly, it states that the "http://www.gnu-pascal.de/current/" web page is a development snapshot, to be used "at your own risk". Is this correct? Isn't that what the "Alpha" and "Beta" directories are for? Secondly, it would be helpful to new visitors if the "download" page also included a link to "http://www.gnu-pascal.de/binary/". After all, new visitors are much more likely to want to download a binary than the source code, so this should be presented to them directly on the "download" page (also, they could easily overlook the "Binary" link at the top of the "Current" web page). Finally, it would also be helpful to new visitors if the notes at the bottom of the "Libraries" section of the "download" page, included a short (one sentence) description of what these libraries actually are. It's all rather cryptic otherwise. Once again, many thanks from all of us, for the great efforts you and the team have made to bring us GPC 2.1 !!! Joe. > -----Original Message----- > From: Frank Heckenbach [SMTP:frank@g-n-u.de] > Sent: Saturday, May 11, 2002 5:21 AM > To: gpc(a)gnu.de; gpc-announce(a)gnu.de > Subject: GPC 2.1 released > > This is the announcement of > > GNU Pascal, version 2.1 > > which is now available from > > http://www.gnu-pascal.de/current/ > > Binaries for some platforms are available in a subdirectory > > http://www.gnu-pascal.de/binary/ > > Binaries for more platforms will follow soon and will be announced > on the GPC mailing list which is archived at > > http://www.gnu-pascal.de/crystal/gpc/en/ > > > About GNU Pascal > ================ > > The GNU Pascal Compiler (GPC) is part of the GNU compiler family, > GNU CC or GCC. It combines a Pascal front-end with the proven GNU C > back-end for code generation and optimization. Unlike utilities such > as p2c, this is a true compiler, not just a converter. > > The purpose of the GNU Pascal project is to produce a Pascal > compiler which > > * combines the clarity of Pascal with powerful tools suitable > for real-life programming, > > * supports both the Pascal standard and the Extended Pascal > standard as defined by ISO, ANSI and IEEE (ISO 7185:1990, > ISO/IEC 10206:1991, ANSI/IEEE 770X3.160-1989), > > * supports other Pascal standards (UCSD Pascal, Borland Pascal, > parts of Borland Delphi and Pascal-SC) in so far as this > serves the goal of clarity and usability, > > * may be distributed under GNU license conditions, and > > * can generate code for and run on any computer for which the > GNU C compiler can generate code and run on. > > Pascal was originally designed for teaching. GNU Pascal provides a > smooth way to proceed to challenging programming tasks without > learning a completely different language. > > The current release GPC 2.1 implements Standard Pascal (ISO 7185, > levels 0 and 1), a large subset of Extended Pascal (ISO 10206, > aiming for full compliance), is highly compatible to Borland Pascal > (version 7.0) with some Delphi extensions, and provides a lot of > useful GNU extensions. > > For more information about GNU Pascal, see > > http://www.gnu-pascal.de > > > Changes since the previous release > ================================== > > The previous release (GPC 2.0) was more than five years ago. Since > then, there have been numerous alpha and beta versions and literally > hundreds of new features and bug fixes. Trying to list them here, > even if only as a summary, would be far beyond the scope of such an > announcement. You can find descriptions of the new features since > 1999-01-18 at > > http://www.gnu-pascal.de/current/news-2.1.html > > and a detailed list of all new features and bug fixes since > 1997-11-01 at > > http://www.gnu-pascal.de/current/done-2.1.html > > In short, a large number of bugs have been fixed, so GPC 2.1 works > much more stable than its predecessor versions. Also, many relics > that made it sometimes look somewhat like a C compiler rather than a > Pascal compiler have been cleared up. > > Compared to GPC 2.0, the support of ISO 7185 Standard Pascal as well > as Borland Pascal has been mostly completed. Borland Pascal support > includes object oriented programming and a set of compatibility > units. > > Much of ISO 10206 Extended Pascal is now supported, including schema > types (i.e., types whose size can vary at runtime), complex numbers, > set extensions and more. > > Some features of other Pascal standards and dialects are supported, > such as operator overloading (Pascal-SC) and some OOP extensions > (Delphi). > > GPC also contains many extensions not found in other Pascal > compilers, e.g. to ease the interfacing with C and other languages > in a portable way, and to work with files, directories, dates and > more, mostly independent of the underlying operating system. > > A number of useful units is included with GPC, such as `RegEx' > (regular expressions), `GMP' (arithmetic with integer, rational and > real numbers of unlimited size), `Trap' (trapping runtime errors), > `Intl' (internationalization), `Pipe' (inter-process communication), > `MD5' (message digests) and many more. GPC includes a number of demo > programs to show the usage of these units and of many compiler > features. > > Further units, Pascal programs and other 3rd party contributions can > be found at > > http://www.gnu-pascal.de/contrib/ > > > Have fun, > > The GNU Pascal development team >

2 1

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 May 2002