Gpc March 2001

gpc@gnu.de

41 participants
73 discussions

Re: "mallinfo" in GPC?
by Prof. A Olowofoyeku (The African Chief) 16 Mar '01

16 Mar '01

On 16 Mar 2001, at 8:13, Tomasz Kowaltowski wrote: > In gcc one can use the function "mallinfo()" in order to know, among > other things, the amount of dynamic storage currently allocated by the > program through "malloc()". I use it to check for program memory leaks. > > I would like to know whether there is anything similar for gpc? Try "AllocMemSize" in the SYSTEM unit (only in the more recent snapshots). Best regards, The Chief --------- Prof. Abimbola Olowofoyeku (The African Chief) Author of Chief's Installer Pro v5.24 for Win32 Email: African_Chief(a)bigfoot.com http://www.bigfoot.com/~african_chief/

1 0

const isn't constant?
by Eike Lange 16 Mar '01

16 Mar '01

Hi! With the following program, I get the error storage size of 'Bar' isn't constant Whats wrong? Is there another way to tell the compiler the storage size of a const value? program test; const Foo : integer = 4; var Bar:array[1..foo] of integer; begin end. Eike

1 0

Rép. : Re: gpc en Mac OS X.
by Blady 15 Mar '01

15 Mar '01

<flushleft><fontfamily><param>Helvetica</param><x-tabstops><param>28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;0L;</param>Hi, I bring now more points on my use of gpc on Mac OS X. I use it with gcc 2.95 but I have still some questions. <bold><x-tabstops><param>72L;144L;216L;288L;360L;0L;</param>1) Dollars in error.pas : </x-tabstops></bold><x-tabstops><param>72L;144L;216L;288L;360L;0L;</param> make CFLAGS="-v -O -DMACOSX -g" ... ../.././xgpc -B../.././ -c -I. -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -v -O -DMACOSX -g -DRTS_RELEASE_STRING="'`cat /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/rts-version`'" --unit-path=/Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts --automake /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas Reading specs from ../.././specs Reading specs from /usr/libexec/ppc/specs Apple Computer, Inc. version cc-2, based on gpc version 20010115, based on gcc-2.95.2 19991024 (release) gcc version 2.95.2 19991024 (release) ../.././gpcpp -lang-pascal -v -I. -famtmpfile=/var/tmp/cc000268 -funit-path=/Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts -fautomake -fdelphi-comments -D__GNU_PASCAL__ -undef -D__GNUC__=2 -D__GNUC_MINOR__=95 -D__GPC__=2 -D__GPC_MINOR__=0 -D__GPC_RELEASE__=20010115 -D__BITS_BIG_ENDIAN__=1 -D__BYTES_BIG_ENDIAN__=1 -D__WORDS_BIG_ENDIAN__=1 -D__ppc__ -D__NATURAL_ALIGNMENT__ -D__MACH__ -D__BIG_ENDIAN__ -D__APPLE__ -D__ppc__ -D__NATURAL_ALIGNMENT__ -D__MACH__ -D__BIG_ENDIAN__ -D__APPLE__ -D__OPTIMIZE__ -g -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -D__STDC__ -D__APPLE_CC__=912 -D__DYNAMIC__ -D__OPTIMIZE__=1 -DMACOSX -DRTS_RELEASE_STRING='20010115' /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas /var/tmp/cc000268.i GNU Pascal Compiler PreProcessor version 20010115, based on gcc-2.95.2 19991024 (release) #include "..." search starts here: #include <<...> search starts here: . /usr/local/include/c++ /usr/local/include /System/Library/Frameworks/System.framework/Headers /usr/include End of search list. ../.././gpc1 /var/tmp/cc000268.i -fforce-mem -Wno-four-char-constants -quiet -dumpbase error.pas -g -O -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -version -famtmpfile=/var/tmp/cc000268 -funit-path=/Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts -fautomake -o /var/tmp/cc000268.s GNU Pascal version 2.95.2 19991024 (release) (powerpc-apple-macosx) compiled by GNU C version 2.7.2.1. GNU Pascal version is actually 20010115, based on gcc-2.95.2 19991024 (release) Reading specs from ../.././specs Reading specs from /usr/libexec/ppc/specs Apple Computer, Inc. version cc-2, based on gpc version 20010115, based on gcc-2.95.2 19991024 (release) gcc version 2.95.2 19991024 (release) ../.././gpcpp -lang-pascal -v -I. -fautomake -funit-path=/Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts -famtmpfile=/var/tmp/cc000268 -fdelphi-comments -D__GNU_PASCAL__ -M -undef -D__GNUC__=2 -D__GNUC_MINOR__=95 -D__GPC__=2 -D__GPC_MINOR__=0 -D__GPC_RELEASE__=20010115 -D__BITS_BIG_ENDIAN__=1 -D__BYTES_BIG_ENDIAN__=1 -D__WORDS_BIG_ENDIAN__=1 -D__ppc__ -D__NATURAL_ALIGNMENT__ -D__MACH__ -D__BIG_ENDIAN__ -D__APPLE__ -D__ppc__ -D__NATURAL_ALIGNMENT__ -D__MACH__ -D__BIG_ENDIAN__ -D__APPLE__ -D__OPTIMIZE__ -g -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -D__STDC__ -D__APPLE_CC__=912 -D__DYNAMIC__ -D__OPTIMIZE__=1 -DMACOSX -DRTS_RELEASE_STRING='20010115' /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/internal.pas -o /var/tmp/cc000271 GNU Pascal Compiler PreProcessor version 20010115, based on gcc-2.95.2 19991024 (release) #include "..." search starts here: #include <<...> search starts here: . /usr/local/include/c++ /usr/local/include /System/Library/Frameworks/System.framework/Headers /usr/include End of search list. Reading specs from ../.././specs Reading specs from /usr/libexec/ppc/specs Apple Computer, Inc. version cc-2, based on gpc version 20010115, based on gcc-2.95.2 19991024 (release) gcc version 2.95.2 19991024 (release) ../.././gpcpp -lang-pascal -v -I. -fautomake -funit-path=/Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts -famtmpfile=/var/tmp/cc000268 -fdelphi-comments -D__GNU_PASCAL__ -M -undef -D__GNUC__=2 -D__GNUC_MINOR__=95 -D__GPC__=2 -D__GPC_MINOR__=0 -D__GPC_RELEASE__=20010115 -D__BITS_BIG_ENDIAN__=1 -D__BYTES_BIG_ENDIAN__=1 -D__WORDS_BIG_ENDIAN__=1 -D__ppc__ -D__NATURAL_ALIGNMENT__ -D__MACH__ -D__BIG_ENDIAN__ -D__APPLE__ -D__ppc__ -D__NATURAL_ALIGNMENT__ -D__MACH__ -D__BIG_ENDIAN__ -D__APPLE__ -D__OPTIMIZE__ -g -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -D__STDC__ -D__APPLE_CC__=912 -D__DYNAMIC__ -D__OPTIMIZE__=1 -DMACOSX -DRTS_RELEASE_STRING='20010115' /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/string.pas -o /var/tmp/cc000271 GNU Pascal Compiler PreProcessor version 20010115, based on gcc-2.95.2 19991024 (release) #include "..." search starts here: #include <<...> search starts here: . /usr/local/include/c++ /usr/local/include /System/Library/Frameworks/System.framework/Headers /usr/include End of search list. /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas: In function `Returnaddr2hex': <bold>/Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas:642: undeclared identifier `$f' (first use in this routine) </bold>/Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas:642: (Each undeclared identifier is reported only once /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas:642: for each routine it appears in.) /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas:642: subrange bounds are not of the same type /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas:642: ordinal type expected /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas:643: incompatible types in initialization /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas:643: initial value is of wrong type <bold>/Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas:650: undeclared identifier `$10' (first use in this routine) </bold>/Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas:654: subscripted object is not an array or string /Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas: In procedure `Signalhandler': <bold>/Users/pascal/Documents/GCC2/gcc-2/gcc/p/rts/error.pas:897: undeclared identifier `$deadbeef' (first use in this routine) </bold>make[1]: *** [error.o] Error 1 make: *** [pascal.rts] Error 2 then I type this that fix it: make CFLAGS="-O -DMACOSX -g -fno-dollars-in-identifiers" <bold>2) lib error : </bold> By default the libm.a library is include in the ld command line so I disable it, since the library is not provided. Modifiction of gpc.c : << #define MATH_LIBRARY "-lm" --- > //#define MATH_LIBRARY "-lm" > #define MATH_LIBRARY "" <bold> 3) link error : </bold> [localhost:~/Documents/CC/essais] pascal% more essai.p program Essai; begin Writeln('Hello World again.'); end. [localhost:~/Documents/CC/essais] pascal% gpc -v essai.p Reading specs from /usr/libexec/ppc/2.95.2/specs Reading specs from /usr/libexec/ppc/specs Apple Computer, Inc. version cc-2, based on gpc version 20010115, based on gcc-2.95.2 19991024 (release) gcc version 2.95.2 19991024 (release) gpcpp -lang-pascal -v -famtmpfile=/var/tmp/cc000323 -fdelphi-comments -D__GNU_PASCAL__ -undef -D__GNUC__=2 -D__GNUC_MINOR__=95 -D__GPC__=2 -D__GPC_MINOR__=0 -D__GPC_RELEASE__=20010115 -D__BITS_BIG_ENDIAN__=1 -D__BYTES_BIG_ENDIAN__=1 -D__WORDS_BIG_ENDIAN__=1 -D__ppc__ -D__NATURAL_ALIGNMENT__ -D__MACH__ -D__BIG_ENDIAN__ -D__APPLE__ -D__ppc__ -D__NATURAL_ALIGNMENT__ -D__MACH__ -D__BIG_ENDIAN__ -D__APPLE__ -D__STDC__ -D__APPLE_CC__=912 -D__DYNAMIC__ essai.p /var/tmp/cc000323.i GNU Pascal Compiler PreProcessor version 20010115, based on gcc-2.95.2 19991024 (release) #include "..." search starts here: #include <<...> search starts here: /usr/local/include/c++ /usr/local/include /System/Library/Frameworks/System.framework/Headers /usr/include End of search list. gpc1 /var/tmp/cc000323.i -Wno-four-char-constants -quiet -dumpbase essai.pas -version -famtmpfile=/var/tmp/cc000323 -o /var/tmp/cc000323.s GNU Pascal version 2.95.2 19991024 (release) (powerpc-apple-macosx) compiled by GNU C version 2.7.2.1. GNU Pascal version is actually 20010115, based on gcc-2.95.2 19991024 (release) /usr/libexec/ppc/as -arch ppc -o /var/tmp/cc0003231.o /var/tmp/cc000323.s /usr/bin/ld -arch ppc -dynamic -lcrt1.o /var/tmp/cc0003231.o -lgpc -lcc_dynamic -framework System /usr/bin/ld: /usr/lib/libgpc.a(error.o) has external relocation entries in non-writable section (__TEXT,__text) for symbols: _memcpy _strlen By this step, I have no more idea. <x-tabstops><param>28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;0L;</param> Is there an explanation for that ? Thank's for your reply, and best whishes for continuation, Pascal Pignard. -------------------------- Le Mardi, Décembre 19, 2000, à 02:36 PM, Frank Heckenbach a écrit : <italic>Hello,</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>> thank's for your reply.</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>> I choose gpc 2.0 release cause of the background release of my cc that is</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>> 2.7.2.1.</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>Yes, this version isn't supported anymore. I.e., you can (probably)</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>compile GPC with gcc-2.7.2.1, but you need the sources of gcc-2.8.1</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>or 2.95.x. Because of increasing internal differences between the</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>gcc versions, we had to drop 2.7.x at some point (and will probably</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>drop 2.8.x sometime next year).</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>> I agree with the fact of using the last release then it becomes more</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>> difficult to</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>> port both cc 2.95 or 3.0 and last gpc.</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>> Though, what are the ports on Mac OS X or Darwin (the unix open souce</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>> layer) ?</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>I'm afraid, I'm not aware of any such ports. If the systems are</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>mostly POSIX compliant (I heard Mac OS X is, and I suppose Darwin is</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>as well), and the backend supports the processor (I'm quite sure it</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>does), and the binutils and system libraries and headers are</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>available (I hope they are), it should not be too difficult to</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>compile the current GCC/GPC versions from sources. There may be</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>problems caused by little incompatibilities, but such problems can</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>usually be sorted out rather easily when you post the error</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>messages. I can't say more at this time...</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>Frank</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>-- </italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>Frank Heckenbach, frank(a)g-n-u.de</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>http://fjf.gnu.de/</italic><color><param>0000,0000,0000</param> <italic></italic></color><italic>PGP and GPG keys: http://fjf.gnu.de/plan</italic><color><param>0000,0000,0000</param> <x-tabstops><param>28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;</param></x-tabstops></color><x-tabstops><param>28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;</param> </x-tabstops></x-tabstops></x-tabstops></x-tabstops></fontfamily></flushleft> F

1 0

Re: Where to place units from the RTS
by david＠tcs01.demon.co.uk 15 Mar '01

15 Mar '01

In message <64B83BAE.20010309232630.FOO-38E5.frank(a)g-n-u.de> Frank Heckenbach writes: > David James wrote: > > > Suppose I have a program that 'uses gpc' (one of the units from the > > GPC RTS). Where should gpc.o and gpc*.gpi be (this is under Linux)? > > And should they have been placed there by the make install when I > > built the compiler? > > > > I'd like to be able to say gpc prog.p and have it automatically find > > the gpc unit at compile time and at link time. At the moment I've > > put gpc.o and gpc*.gpi in the same directory as the program, and am > > specifying gpc.o in the command line, but there must be a neater way > > of doing it ... > > The source of the units should remain in the directory where they're > installed, i.e. <prefix>/lib/gcc-lib/<target>/<gcc-version>/units. That's /usr/local/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/units in my case. > If GPC was built correctly, it should find them there automatically > (try `gpc --print-file-name=units' if not). which shows the directory above. [snip] > --automake > compile units when necessary and link their object files > automatically, so you won't have to specify gpc.o on the command > line Removing gpc.pas, gpc*.o, and gpc*.gpi from my own source directory and using --automake allows the compile and link to succeed. > > --unit-path=DIR:DIR:... > search path for other units, i.e. not those shipped with GPC (they > should be found automatically) and not in the current directory -- I still have a problem here ... for me GPC (20010306) is not finding units in the current directory at link-time. For example: helunit.p ========= unit helunit; interface procedure writeit; implementation procedure writeit; begin writeln('Hello from unit'); end; end. ======== useunit.p ========= program useunit(output); uses helunit; begin writeln('Hello world, and now ... from the unit'); writeit; writeln(' ... and back in main'); end. ======== If I say gpc -c helunit.p and then gpc useunit.p I get: /tmp/cc2caGt51.o: In function `pascal_main_program': /tmp/cc2caGt51.o(.text+0x32): undefined reference to `Writeit' /tmp/cc2caGt51.o: In function `init_pascal_main_program': /tmp/cc2caGt51.o(.text+0x7f): undefined reference to `init_Helunit' collect2: ld returned 1 exit status >From what you say above, I would have expected this to work, and it *did* work with GPC 19991030. Is this the expected behaviour? (I could set --unit-path to include the current directory, but you seem to be saying that should not be necessary.) -- David James mailto:david@tcs01.demon.co.uk Special Stage Rally results archive <URL:http://www.tcs01.demon.co.uk/>

2 1

Re: GNU Pascal Anfänger
by Dieter Schmitz 14 Mar '01

14 Mar '01

Hello, The German GPC Mailinglist is ready to use. to subscribe send a mail to majordomo(a)gnu.de with the message subscribe gpc-de in the body part, the rest you should know. If you want to write to the list send your mail at gpc-de(a)gnu.de -- Greetings Dieter

1 0

None
by Dieter Schmitz 14 Mar '01

14 Mar '01

1 0

Learning tool for GPC and Forgotten FTP password
by Patrick Sharp 14 Mar '01

14 Mar '01

Greeting all! About 4 years ago, I wrote several units for GPC. There were some BP5-7 compatibility units and few wrapper units for Panels, MySql, SoundIT and others. The BP stuff was almost complete, with panel support included with the CRT units (message box like). This was a work in progress that had functioned perfectly... with the version of GPC that was alive in '97 :) All of this source was deleted, and I had no other copies of it... until last week when, by chance, the ISP that I was using (way) back then called me. They were cleaning off old backups and noticed that I still had source files on their server. Lucky for me the president of that company is a GPC fan, and decided to save this file off for me! Now for the point of all of this. My intention was to upgrade all of these units to work with the newest version of GPC. My problem is that the company I work for now does not (yet :)) want to provide any GNUish code for the public and has (sadly) decided to move everything over to Borland's Kylix.. These units were always meant to be released to the GNU community, and I believe that it would be a shame to let them go again.. IF anyone is interested in learning about GPC and Pascal, I believe that this could be a good resource for it. This code will not compile under the current version of GPC, but all of it could be easily upgraded. It's mostly a problem with types like _cstring and such. For now, I will place it on www.cyberconfused.com/gpc_stuff.tgz and if there is any interest in this source at all, I will place it on the agnes server. There is no real site here as I have lost interest in designing anything for it and since I can never seem to get anonymous FTP working with my server, you will need to get this with your browser.. Sorry about that. **PETER. I have lost my ftp password for the psharp account on agnes. I don't know if you keep records of this stuff, but you know me as psharp(a)nilenet.com and also from some of the programs in the test suites (some of the string tests). Is this something that you can email to me?? Thanks! Patrick Sharp Community Webs Inc. 7211 So. Colorado CT. Littleton CO, 80122 pat(a)communitywebs.com http://www.communitywebs.com

2 1

chown? was it going to be posted to the gnu pascal site?
by jallan 14 Mar '01

14 Mar '01

Hey Peoples, I was very greatful for the code to be able to use crypt()... just wondering if the code to be able to use chown() is on the gnu pascal website yet. Jamie

2 1

Re: delphi equivalents in GPC
by Prof. A Olowofoyeku (The African Chief) 13 Mar '01

13 Mar '01

On 13 Mar 2001, at 9:43, Kocherlakota Harikrishna wrote: > Hello, > I would like to know the equivalents for the following delphi > commands/types/functions/units in GPC(on Linux) > Â > > * Tdatetime > * decodetime > * decodedate > * swap > * extractfilename > * expandfilename > * messagebox > * sysutils > * thandle For an early version of the Sysutils unit, see: ftp://agnes.dida.physik.uni-essen.de/home/chief/sysutils-20000725.zip That version will not compile with the most recent GPC snapshots without some minor amendments. If anyone is interested, I can release a more up- to-date version. MessageBox is a WinAPI function. To use something like that under Linux you will need to write a wrapper for some X apis. Best regards, The Chief --------- Prof. Abimbola Olowofoyeku (The African Chief) Author of Chief's Installer Pro v5.24 for Win32 Email: African_Chief(a)bigfoot.com http://www.bigfoot.com/~african_chief/

1 0

Re: GNU Pascal Anfänger
by Prof Abimbola Olowofoyeku 13 Mar '01

13 Mar '01

On 10 Mar 01, at 7:00, Egbert Seibertz wrote: [...] > But if something interesting comes up in their list, the rest of us on > the > main list would miss out. > > if it's really importent, they'll tell us! How would they know what is "really important" to me (or you?). Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) Author of: Chief's Installer Pro for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm Email: African_Chief(a)bigfoot.com

4 6

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 March 2001