Gpc

gpc@gnu.de

5400 discussions

crt library for GNU?
by Ian Maddox 09 Feb '00

09 Feb '00

I am a high-school student using the Gnu pascal compiler for programming homework, but I run into a regrettable hitch. My programs are now requiring the Borland Pascal crt library, and I don't know where to find either that library or a similar one for GNU. Is there any hope? ((The crt library is responsible for clearing the screen, creating sounds and colors on the screen, and random numbers, I think.)) Thanks for your help... Ian Maddox

2 1

List archive working again
by Anja Drewitz 08 Feb '00

08 Feb '00

Hello, the list archive at should be working again now. The URL is http://www.gnu.de/archive/wilma.cgi/gpc and http://www.gnu.de/archive/wilma.cgi/gpc-announce respectively. Now the pages also come in gpc signature colors. :-) Currently, the search option is working fine. If you find it broken, please email me at <anja(a)drewitz.de>. Please don't mail a copy to the gpc list because I let procmail move all mails with To: gpc... and Cc: gpc... to a separate folder and would not see your mail for a long time. Best wishes, Anja

1 0

Failure when using crt unit
by Klaus Friis Østergaard 08 Feb '00

08 Feb '00

I get this failure when I try to compile a program that uses the crt unit program test; uses crt; ... begin .. end. I call gpc with this gpc -O --automake --extended-syntax test.pas -o test I get this failure: gpc: installation problem, cannot exec 'cpp': no such file or directory gpc1: gpc exits with status 1 /usr/lib/gcc-lib/i386-rehat-linux/2.8.1/crt.pas:345 '/usr/lib/gcc-lib/i386-rehat-linux/2.8.1/crtc.c' could not be compiled modul crt could not be compiled I have run the test with make which uses units the standard units which is descibed in the documentation of the beta relaese , should be read automatically. Does anybody seen this problem and what shal I do to fix it? Klaus F. Ãstergaard

2 1

External (asmname) variables (was: rough draft - FAQ
by Dr Abimbola A Olowofoyeku 04 Feb '00

04 Feb '00

On 3 Feb 00, at 14:39, Peter Gerwinski wrote: > Matze Braun wrote: > > You should add, how to use global vars from C-Librarie. I had to > > look for a long time before I noticed, that I have to use asmname > > '...' before the Data Type. > > I often thought about > > - replacing `asmname' by `external name' (inspired by DLL > support in BP), I am strongly in favour of that. > - making `external' a rigidly reserved word, so we can place > it _after_ the type. Good idea! Best regards, The Chief -------- Dr. Abimbola A. Olowofoyeku (The African Chief) Author of: Chief's Installer Pro v5.21.1 for Win32 http://ourworld.compuserve.com/homepages/African_Chief/chief32.htm

1 0

Re: Compiling gpc-19991030 fails on rts.c
by Frank Heckenbach 04 Feb '00

04 Feb '00

Dr A Olowofoyeku wrote: > Here is the fsync function. I get compile errors when converting it to > a macro in os-hacks.h - so please convert it for me. > > int fsync (int __fd) > { > return FlushFileBuffers ((HANDLE) _get_osfhandle (__fd)); > } I don't know all the relevant declarations, but normally, the following should work: #define fsync(__fd) (FlushFileBuffers ((HANDLE) _get_osfhandle (__fd))) If it doesn't, please show me the error messages. BTW, does FlushFileBuffers return 0 on success and -1 on error? If it returns 1 on success and 0 on error (as some Windoze routines do IIRC), try: #define fsync(__fd) ((FlushFileBuffers ((HANDLE) _get_osfhandle (__fd))) ? 0 : -1) > > getpwnam, getpwuid - get password file entry > > Here is my implementation. The WinAPI calls are correct, but I am > clearly not doing things correctly as far as the return values for > pointers to the passwd structure is concerned - I get garbabe in the > fields when I call the functions that return pointers to the passwd > structure (but inside the functions themselves, when I do "printf" of > the return values from the WinAPI functions, I get correct values). > So the problem is how to assign the values returned by WinAPI to > the fields of the structure, and how to return correctly. This is because local variables (can) become invalid after the function returns which is problematic if you return a pointer to them. To solve it, declare them as `static'. AFAICS, this affects the following variables: char fcc[260]; WCHAR wname[256]; struct passwd psw; struct passwd psw; struct passwd psw1; BTW: The statment `psw0 = malloc (sizeof (*psw0));' seems to be superfluous as psw0 is overwritten two lines below. Another thing, in the function: char *wide2ansi (LPWSTR wide) { char fcc[260]; fcc[0] = NULL; WideCharToMultiByte ( CP_ACP, 0, wide, -1, fcc, 260, NULL, NULL ); return &fcc; } The `&' should be omitted (in C, arrays are automatically treated as pointers when necessary -- though it seems to work with the `&' as well, but produces a warning). 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: Compiling gpc-19991030 fails on rts.c
by Frank Heckenbach 04 Feb '00

04 Feb '00

Dr A Olowofoyeku wrote: > On 23 Jan 00, at 2:17, Frank Heckenbach wrote: > > > J. David Bryan wrote: > > > > > On 21 Jan 00, at 9:58, Dr A Olowofoyeku wrote: > > > > > > > Your problem is probably due to things that are missing in the gcc Mingw > > > > libraries (and there are many of them). > > > > > > I have tracked my specific problem down to the lack of a "pwd.h" file in > > > Mingw (thanks, Chief!). The trouble is that "_p_pwl2c" in "rts.c" > > > references the "passwd" struct, which is defined in "pwd.h", but "pwd.h" > > > isn't part of Mingw. This is detected by the Pascal "configure", which > > > sets "#undef HAVE_PWD_H" in "rts-config.h" but is not covered by alternate > > > code in "rts.c". The result is a syntax error when compiling. > > > > As I said, the current code (to be released as a snapshot soon) > > contains such a check. However, no alternate code (just a failure > > result) -- if there's equivalent functionality on other systems > > (which I don't know about), I'll have to leave it to you to add > > it... > > Can you please let me know what the code is actually supposed to > do? Perhaps there is a way to write an implementation for it, which > we can include in 'os-hacks.h'. It returns information about the user accounts on the system (i.e., not the users currently logged in, but all users who are allowed to log in). I guess on MS-Windows 95/98, there's not much point to it, but on NT, there might be... The relevant functions and data types are: --- NAME getpwnam, getpwuid - get password file entry SYNOPSIS #include <pwd.h> #include <sys/types.h> struct passwd *getpwnam(const char * name); struct passwd *getpwuid(uid_t uid); DESCRIPTION The getpwnam() function returns a pointer to a structure containing the broken out fields of a line from /etc/passwd for the entry that matches the user name name. The getpwuid() function returns a pointer to a structure containing the broken out fields of a line from /etc/passwd for the entry that matches the user uid uid. The passwd structure is defined in <pwd.h> as follows: struct passwd { char *pw_name; /* user name */ char *pw_passwd; /* user password */ uid_t pw_uid; /* user id */ gid_t pw_gid; /* group id */ char *pw_gecos; /* real name */ char *pw_dir; /* home directory */ char *pw_shell; /* shell program */ }; RETURN VALUE The getpwnam() and getpwuid() functions return the passwd structure, or NULL if the matching entry is not found or an error occurs. --- NAME getpwent, setpwent, endpwent - get password file entry SYNOPSIS #include <pwd.h> #include <sys/types.h> struct passwd *getpwent(void); void setpwent(void); void endpwent(void); DESCRIPTION The getpwent() function returns a pointer to a structure containing the broken out fields of a line from /etc/passwd. The first time it is called it returns the first entry; thereafter, it returns successive entries. The setpwent() function rewinds the file pointer to the beginning of the /etc/passwd file. The endpwent() function closes the /etc/passwd file. The passwd structure is defined in <pwd.h> as follows: struct passwd { char *pw_name; /* user name */ char *pw_passwd; /* user password */ uid_t pw_uid; /* user id */ gid_t pw_gid; /* group id */ char *pw_gecos; /* real name */ char *pw_dir; /* home directory */ char *pw_shell; /* shell program */ }; RETURN VALUE The getpwent() function returns the passwd structure, or NULL if there are no more entries or an error occurs. --- So, getpwnam and getpwuid find an entry by user name or user ID, resp., while getpwent returns all entries successively. Of course, the former to can be implemented on top of the latter, so if only the latter is available, that'll be fine. BTW, the pw_passwd contains the password in encrypted form, of course! And on systems that use shadow, it doesn't contain anything interesting (at least for normal programs), but usually `*' or `x'. That's better security-wise, so you probably shouldn't even try to put something interesting in this field... If it's not possible to implement them, don't worry. These functions will by marked as optional (i.e., not returning meaningful information on all systems), and programs are expected to cope with that (which will appear to them like a system with no accounts). 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

2 1

Re: rough draft - FAQ
by Frank Heckenbach 03 Feb '00

03 Feb '00

Russ Whitaker wrote: > attached is a rough draft of a FAQ. Will add about the Solaris 8 > binaries. Any additions, corrections, comments? OK, here are some... > Is it compatible with Turbo Pascal (R) ? > ======================================== > > GPC is currently *not* a drop-in replacement for Borland's Turbo > Pascal (R). It supports a number, but not all of the Borland > extensions to the Pascal language. There is no replacement for most of > the Borland runtime library functions. GNU Pascal is part of the GNU > project, so portability is one of its primary goals. For this reason, > non-portable features of Borland Pascal will probably not be included > into GNU Pascal. More information can be found in the section "Borland > Pascal" of the GPC manual. This has changed a lot. Almost all BP language features are supported now. Notable exceptions are the string format (as discussed below), or the `Mem' and `Port' pseudo arrays, though replacement functions for the latter on x86 platforms exist in the `Ports' unit. Also, almost all of BP's run time library is supported in GPC (built-in or in units with the same names as their BP counterparts). Some notes: - A BP compatible Graph unit exists, but is distributed separately due to its license. - The OOP stuff (Turbo Vision etc.) is not yet completed, but work on several projects is underway. - Some exotic routines need an explicit `uses System' statement, or equivalently a `--uses=system' command line option. See the system unit for details. - A few unportable routines are not supported in the Dos unit (see the comments there). I think there's an older, unportable, Dos unit which supports them (or else it's easy to write one) if you really need those routines... > When I build `libgpc.a', `rt0.c' says: SIGXCPU undefined (and more) > ======================================================================= I'm adding an autoconf test to overcome this problem, so I think you can remove the item after the next release. > Can you recommend an IDE? > ========================= > > Users of Borland Pascal may wonder if there's a replacement for the > IDE (Integrated Development Environment). Here's a few suggestions: > > * (X)Emacs. Some people think it's the answer to the question of > Life, the Universe and Everything, others decide it's uGNUsable. > Available from your friendly GNU mirror. > > * XWPE is an imitation of the Borland IDE, so users of Borland > Pascal may find it a good alternative. > > * RHIDE. djgpp users should definately try RHIDE. The latest (beta) > release is compatible with GNU Pascal and allows stepping, tracing > and watching like Borland's IDE. RHIDE v0.6 beta can be downloaded > from: > http://www.tu-chemnitz.de/~rho/rhidetest.html The URL has changed to: http://www.tu-chemnitz.de/~sho/rho/rhide/rhide.html Also, I'd like to plug my own IDE, PENG. It's not free software, but it was written with GPC. It's also very similar to Borland's IDE, but with many extensions: http://fjf.gnu.de/peng.html > Do you have a binary for me? > ============================ > > Currently, we have binaries for these platforms: > > i486-linux (ELF) > i486-linuxaout > i486-linuxoldld > i386-freebsd1.2.0 > djgpp V2 (msdos) > emx 0.9B (OS/2, msdos) > cygwin32 beta16 (Windows95, Windows NT) > mips-sgi-irix5.3 > sun-sparc-sunos4.1.4 > > New binaries may have been added after the release of this FAQ. You might want to update the list by looking at the FTP directory beta/binary on agnes. > 3.0 GNU Pascal and your system libraries > **************************************** > > This section discusses common problems people have when they try to > access their system's libraries. > > How do I use <insert_your_function_here> from the C library? > ============================================================ > > GNU Pascal can use every function of your C library, but it may be > up to you to write declaration of an external function, before you can > use it. Consider the function `sleep'. `man(3) sleep' reveals: > > --------------------------------------------------------- > NAME > sleep - Sleep for the specified number of seconds > > SYNOPSIS > #include <unistd.h> > > unsigned int sleep(unsigned int seconds); > --------------------------------------------------------- > > This small demo program shows how to use `sleep' in a Pascal program: > > --------------------------------------------------------- > program SleepDemo; > > type > word = __unsigned__ integer; > > function sleep(seconds: word): word; C; > > var > result : word; > > begin > result := sleep(10); > end. GPC knows the type `Word' (and, for that matter, equivalent built-in types for all integer types in C). `__unsigned__' is considered obsolete and will probably removed soon, so using the built-in `Word' (or `Cardinal' which is the same) is recommended (see the subsection `Integer Types' in the GPC manual). Also, as Peter mentioned, GPC by now provides routines for many libc functions. Most of them are declared in the GPC unit (see the section `Run time library' in the chapter `Programming' in the GPC manual for complete declarations). `Sleep' is one of them, and using the one from the GPC unit is recommended, because it's more portable. > How do I build/use a shared library? > ==================================== > > (topic under construction) Using them is easy: Just add the appropriate `-lfoo' option to the command line, or (more recommended) a `{$L foo}' compiler directive (where `foo' is the name of the library) into the program or a unit. This will use a shared library by default, and a static one if a shared library is not found or the command line option `-static' is given. Creating a shared library currently works like in GCC, e.g. by linking the object files with `-shared'. You will have to take care about the interfaces yourself, since GPI files are not handled, and you might have to explicitly call any unit/module initializers. There is support for building the GPC runtime library (libgpc) dynamically, by configuring the RTS (not the compiler!) with `--with-shared', which can reduce the size of executables dramatically, but since it makes the executables dependent on the shared library version and the runtime library is changing fast, this is currently considered "on your own risk". Don't do it if you intend to distribute your binaries. Note that some platforms, e.g. DJGPP, don't support shared libs at all. > However, the > Pascal string schema, as defined in section 6.4.3.3.3 of the ISO-10206: > 1990 Extended Pascal standard, is a record: > > type string = record > Capacity : integer; > length : integer; > string : packed array [ 1..Capacity ] of char; > end; Actually it's a schema record: type String (Capacity : integer) = record Length : 0 .. Capacity; String : packed array [1 .. Capacity + 1] of Char end; The `+ 1' is a GPC extension to make it feasible to automatically add the #0 terminator when passing or assigning them to CStrings. > In standard pascal you expect ic[1] to align > with the first character position of s and thus one character to the left > is the length of s. Thus ic[0] is the length of s. True? Better add a "Q:" here, otherwise careless readers might take the "standard pascal" bit as a true statement... > There may be other ways to do the same thing; you could declare a > type `PChar' instead of `CString': > > type > PChar = ^char; > > and replace all references to `CString' with `PChar'. Do *NOT* pass > a "C" style string as a var-argument if the C prototype says `const > char *' or you will get a coredump. > > You are right if you think this stuff belongs in a library, to be > distributed with GPC. Have patience, or start coding! `PChar' is predefined now (though we recommend `CString' because it makes it clearer that we're talking about some kind of string rather than a single character), and a lot of library routines in Pascal for many applications (in the GPC unit and some other units) have been written (see above)... > At least for some of the pre-releases of `gpc-1.2', the > `gpc.info' file is invalid: it refers to the `gpc.i*' sections as > `gpc.info-*'. This can be fixed by loading `gpc.inf' in an editor and > replacing `gpc.info-*' with `gpc.i*' I think that's obsolete. :-) > A guide is available which was written by Brennan Mr. Wacko Underwood > <brennan(a)mack.rt66.com> and describes how to use inline assembly > programming with DJGPP, at this URL: > > http://www.rt66.com/~brennan/djgpp/djgpp_asm.html There's also a GPC assembler tutorial at ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/gpcasm.zip > type > word = __unsigned__ integer; > short = __short__ integer; > byte = __byte__ integer; See above. (`Byte' and `Word' are built-in, and `ShortInt' is `short' in C.) > Bugs are best reported to the GPC mailinglist <gpc(a)hut.fi>. > > You can send a message to the GPC mailing list by sending email to > the list address <gpc(a)hut.fi> as if it were a person. > > You can join the mailing list by sending a message to > <gpc-request(a)hut.fi> (NOT <gpc(a)hut.fi> !) with your request to be added > to the list. Maintenance is done by hand, so some delay is possible. > > To leave the mailing list, send a message to <gpc-request(a)hut.fi>. s/hut.fi/gnu.de/ :-) Maintenance is automatic now. > 7.0 Miscellaneous > ***************** > > I want to contribute; where do I start? > ======================================= > > A list of jobs which should be done for GNU-Pascal can be found in > the section "How to contribute" of the Texinfo deocumentation. In cases > where somebody is already working on a topic, the name of that person is > written behind the job's description. This is hopelessly outdated (and I think has been removed from the distribution now). For now, if you want to contribute, please write to the mailing list. > The master FTP site for GNU Pascal is `kampi.hut.fi'. GNU Pascal > related files can be found in: > > ftp://ftp.kampi.hut.fi/jtv/gnu-pascal/ > > This site is mirrored on: > > ftp://sunsite.doc.ic.ac.uk/gnu/pascal/ > > The latest developer releases can be downloaded from: > > ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/ agnes is now the master FTP site rather than kampi. > Also, we have a homepage on the web: > > http://agnes.dida.physik.uni-essen.de/~gnu-pascal/ Or shorter: http://home.pages.de/~GNU-Pascal/ 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

rough draft - FAQ
by Russ Whitaker 03 Feb '00

03 Feb '00

Hi all attached is a rough draft of a FAQ. Will add about the Solaris 8 binaries. Any additions, corrections, comments? Thanks Russ <russwhit(a)mind.net> ********************************************************************* GNU Pascal Frequently-Asked Questions List, Edition 0.5, February 2000 by Russ Whitaker <russwhit(a)mind.net> based on GNU Pascal Frequently-Asked Questions List, Edition 0.4, for GPC version 2.0, November 1996 by J.J. van der Heijden <j.j.vanderheijden(a)student.utwente.nl> For up-to-date information, ask the GPC mailing list (see below). Index ***** 1.0 GNU Pascal - what, where and why 2.0 Installation 3.0 Pascal and system libraries 4.0 Strings 5.0 Pascal on the djgpp platform 6.0 Getting Help 7.0 Miscellaneous 1.0 GNU Pascal *************** 1.1 What and why? ================= The purpose of the GNU Pascal project is to produce a Pascal compiler (called GNU Pascal or GPC) 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, Pascal-SC) in so far as this serves the goal of clarity and usability, * may be distributed under GNU license conditions * can generate code and run on any computer for which the GNU C compiler can generate code and run. Pascal was originally designed for teaching. GNU Pascal provides a smooth way to proceed to challenging programming tasks without learning a completely different language. 1.2 What is the current version? ================================ The latest release as of this writing is GPC-19991030. GPC requires GCC as a back-end. Patches for GCC 2.8.1 thru GCC 2.95.2 are provided but it is recommended that you use at least GCC 2.95. 1.3 Where can I get it? ======================= You can download the latest alpha or beta releases of gpc from ftp://agnes.dida.physik.uni-essen.de/ Is it compatible with Turbo Pascal (R) ? ======================================== GPC is currently *not* a drop-in replacement for Borland's Turbo Pascal (R). It supports a number, but not all of the Borland extensions to the Pascal language. There is no replacement for most of the Borland runtime library functions. GNU Pascal is part of the GNU project, so portability is one of its primary goals. For this reason, non-portable features of Borland Pascal will probably not be included into GNU Pascal. More information can be found in the section "Borland Pascal" of the GPC manual. Also see "About Strings", below. 2.0 Installation related questions ********************************** This section discusses some common problems with the installation of GNU Pascal. Which platforms are supported by GNU Pascal? ============================================ GPC uses the GCC backend, so it should run on any system that is supported by GNU CC. This includes a large variety of Unix systems, MS-DOS, OS/2 and Win32. A full list of platforms supported by GCC can be found in the file `INSTALL' of the GCC distribution. Not all of these have actually been tested, but it is known to run on these platforms: ix86-linux (Linux 2.x, ELF) i486-linuxaout i486-linuxoldld i386-freebsd1.2.0 djgpp V2 (msdos) emx 0.9B (OS/2, msdos) cygwin32 beta16 (Windows95, Windows NT) mips-sgi-irix5.3 sun-sparc-sunos4.1.4 >>> Ok people - send us your success stories, with canonical machine name! <<< Which components do I need to compile Pascal source code? ========================================================= A complete Pascal compiler system should at least have: 1. The actual compiler, GPC. While there are some binaries available you can build GPC yourself. You nee a working C compiler, some tools: bash, ar, patch, make, the GCC source, and the GPC source. 2. An editor, Assembler, linker, librarian and friends. 3. A C library. If you have a working C compiler you already have this. 4. A debugger, if you want to debug your programs. For most people, the GNU binutils and GNU debugger (gdb) are a good choice, although some may prefer to use vendor specific tools. How do I build a GPC compiler? ============================== If you have a typical ix86 box the routine is fairly simple. Any other computer you should carefully read the documentation in GCC*/install. Assuming you have: 1. A working C compiler. 2. The usual tools: ar, awk, bash, bison, ld, make, patch, sed 3. The GPC and GCC tar.gz source in directory /usr/local/src Then here's a cookbook recipe: 1. Unpack the two sources: tar -xvzf gcc-2.95.2.tar.gz tar -xvzf gpc-19991030.tar.gz 2. Since GCC recommends building gcc in a separate directory, lets make one: we'll call it gcc-build. mkdir gcc-build 3. Now we need to move GPC into GCC: mv gpc/p gcc-2.95.2/gcc 4. Next is a patch to gcc: cd gcc-2.95.2/gcc patch -s -p1 < p/diffs/gcc-2.95.2.diff 5. Now GCC is ready to build several languages, including pascal. If you want to know what languages, grep language= */config-lang.in will give you a list. 6. So let's go do it: cd ../../gcc-build ../gcc-2.95.2/configure --enable-languages=pascal make bootstrap-lean That "make bootstrap-lean" will take some time. If you want to know how much, you could date > /time1 ; make bootstrap-lean ; date > /time2 On my 400mhz i586 with 128m ram, no swap, it took 24 min 34 sec. 7. If all went well you can now install it: make install That's it. You can find some interesting demos in /usr/local/doc/gpc/demos and you can find the units directory with find /usr/local/lib -name units note: the following six items are untouched from the original FAQ Help! linking `gpc1' fails: `_emit_string_move' undefined (and more) ==================================================================== If linking `gpc1' bombs out with an error message that looks like this: ld: Undefined symbol _emit_string_move _emit_string_pad _maybe_find_function_data _dbxout_set_type_status _version_flag *** Error code 1 make: Fatal error: Command failed for target `gpc1' you probably suffer from a VPATH make problem. A few GPC source files have counterparts with identical name in the GCC source directory. When you have built GCC in the GCC source directory and you are not using a recent version of GNU make this problem may occur. There are three solutions: 1. Get a recent version of GNU make. Version 3.74 or better is known to work. 2. Build GCC in a seperate directory instead of using the GCC source directory. 3. Manually delete these files from the GCC object directory: `stor-layout.o' `dbxout.o' `expr.o' `fold-const.o' `optabs.o' `convert.o' `function.o' `setop.o' `toplev.o' then resume `make'. When I build `libgpc.a', `rt0.c' says: SIGXCPU undefined (and more) ======================================================================= Compilation of the runtime system may fail in `rt0.c' with a message simular to this: rt0.c: `SIGXCPU' undeclared (first use this function) or: rt0.c: storage size of `sv' isn't known rt0.c: storage size of `osv' isn't known If this happens to you, you probably have run the `configure' script with the `--with-bsdrts' option while your Unix is not fully BSD compliant. The solution is to rerun `configure' without the `--with-bsdrts' switch. I'm using Unix, and all my Pascal programs have linking problems. ================================================================= A number of Unix configurations use their system's linker instead of GNU `ld'. Usually, GPC and GCC need a program called `collect2' before calling the system's `ld'. `collect2' is installed by GCC, and if you only install GPC, it will not find `collect2', and use the system linker directly, which will result in various linker errors. The solution is to copy `collect2' by hand from the GCC directory to the location where `gpc1' lives. How do I debug my Pascal programs? ================================== To debug your programs, (a) GNU Pascal must be able to generate executables with debug info for your platform, and (b) you must have a debugger which understands this. * If `gpc -g -o hello hello.p' says: `gpc: -g not supported for this platform', then GPC is unable to generate debug info. Usually, installing GAS instead of your system's assembler can overcome this. When you configure the GCC used for GPC, specify `-with-gnu-as', and possibly `-with-gnu-ld' and/or `-with-stabs'. More information can be found in `INSTALL' file in the GNU CC source directory. * Your system's debugger may not understand the debug info generated by GNU tools. In this case, installing GDB may help. The bottom line: if you can debug GCC compiled programs, you should be able to do this with GPC too. The GNU debugger (GDB) currently does not have a "Pascal" mode, so it is unable to display certain Pascal structures etc. When debugging, please note that the Initial Letter In Each Identifier Is In Upper Case And The Rest Are In Lower Case. If you want to display variable `foo' in the debugger, type `show Foo' or `display Foo' instead. Can you recommend an IDE? ========================= Users of Borland Pascal may wonder if there's a replacement for the IDE (Integrated Development Environment). Here's a few suggestions: * (X)Emacs. Some people think it's the answer to the question of Life, the Universe and Everything, others decide it's uGNUsable. Available from your friendly GNU mirror. * XWPE is an imitation of the Borland IDE, so users of Borland Pascal may find it a good alternative. * RHIDE. djgpp users should definately try RHIDE. The latest (beta) release is compatible with GNU Pascal and allows stepping, tracing and watching like Borland's IDE. RHIDE v0.6 beta can be downloaded from: http://www.tu-chemnitz.de/~rho/rhidetest.html Although GDB is an excellent debugger, it's user interface is not very attractive. Refer to the comp.windows.x FAQ: "Where can I get an X-based debugger?" at: http://www.cis.ohio-state.edu/hypertext/faq/usenet/x-faq/part6/faq-doc-2.htm l Some useful frontends include: XXGDB, tGDB and XWPE. see: http://www.ee.ryerson.ca:8080/~elf/xapps/Q-IV.html Very nice, but resource consuming is the Motif based DDD: http://sol.ibr.cs.tu-bs.de/softech/ddd/ Do you have a binary for me? ============================ Currently, we have binaries for these platforms: i486-linux (ELF) i486-linuxaout i486-linuxoldld i386-freebsd1.2.0 djgpp V2 (msdos) emx 0.9B (OS/2, msdos) cygwin32 beta16 (Windows95, Windows NT) mips-sgi-irix5.3 sun-sparc-sunos4.1.4 New binaries may have been added after the release of this FAQ. 3.0 GNU Pascal and your system libraries **************************************** This section discusses common problems people have when they try to access their system's libraries. How do I use <insert_your_function_here> from the C library? ============================================================ GNU Pascal can use every function of your C library, but it may be up to you to write declaration of an external function, before you can use it. Consider the function `sleep'. `man(3) sleep' reveals: --------------------------------------------------------- NAME sleep - Sleep for the specified number of seconds SYNOPSIS #include <unistd.h> unsigned int sleep(unsigned int seconds); --------------------------------------------------------- This small demo program shows how to use `sleep' in a Pascal program: --------------------------------------------------------- program SleepDemo; type word = __unsigned__ integer; function sleep(seconds: word): word; C; var result : word; begin result := sleep(10); end. ---------------------------------------------------------- Are GNU Pascal objects compatible with GNU C++ classes ? ======================================================== No. (This may change in a future version) How do I build/use a shared library? ==================================== (topic under construction) 4.0 STRINGS *********** What's this confusion about strings? ==================================== Turbo Pascal strings have a length byte in front. Since a byte has the range 0 - 255, this limits a string to 255 characters. However, the Pascal string schema, as defined in section 6.4.3.3.3 of the ISO-10206: 1990 Extended Pascal standard, is a record: type string = record Capacity : integer; length : integer; string : packed array [ 1..Capacity ] of char; end; Thus at the expense of a little added complexity ( must declare capacity, don't use GetMem, and the additional space requiremnent ) you can now have very long strings. The following Q&A is also about strings: ======================================== Q: Should the different variants in a variant record overlay in the same memory? Previous Pascals I have used have guaranteed this, and I've got low-level code that relies on this. The variants are not the same length, and they are intended not to be. A: No, this is intentional so that the discriminants are not overwritten, and they can be properly initialized in the first place. Consider: record case Boolean of False: (s1 : String (42)); True: (s2 : String (99)); end; If the strings would overlay, in particular their disriminants would occupy the same place in memory. How should it be initialized? Either way, it would be wrong for at least one of the variants... So, after a discussion in comp.lang.pascal.ansi-iso where this topic came up concerning file variables (which also require some automatic initialization and finalization), we decided to do this in GPC for all types with automatic initialization and finalization (currently files and schemata, in the future this might also be Delphi compatible classes and user-defined initialized and finalized types), since the standard does not guarantee variants to overlay, anyway... There are two ways in GPC to get guaranteed overlaying (both non-standard, of course, since the standard does not assume anything about internal representations; both BP compatible), `absolute' declarations and variable type casts. E.g., in order to overlay a byte array to a variable v: var b: array [1 .. SizeOf (v)] of Byte absolute v; or type t = array [1 .. SizeOf (v)] of Byte; then `t (v)' can be used as a byte array overlayed to v. In standard pascal you expect ic[1] to align with the first character position of s and thus one character to the left is the length of s. Thus ic[0] is the length of s. True? This holds for UCSD/BP strings (which GPC does not yet implement, but that's planned). The only strings Standard Pascal knows are arrays of char without any length value. Q: Two different kinds of strings with the same name - string - does make a bit of confusion. Perhaps the oldstyle strings could be renamed "short string" ? A: When we implement the short strings, we'll have to do such a distinction. Our current planning goes like this: string (n): string schema (EP compatible) string [n]: short string (UCSD/BP compatible, where n must be <= 255) string: dependent on flags, by default undiscriminated schema, but in BP mode (or with a special switch) short string of capacity 255 (UCSD/BP compatible). ---- Frank Q: So when will these short strings be available? A: It's been planned for over a year. The delay has been caused by more pressing problems. What about C strings? ===================== A C string (`char *') is an array of char, terminated with a `NULL' char. C library functions require C, not Pascal style string arguments. However, Pascal style strings are automatically converted to C style strings when passed to a routine that expects C style strings. This works only if the routine reads from the string, not if it modifies it. E.g., this is how you access the `system()' call in your C library (which is not necessary any more, since `Execute' is already built-in): --------------------------------------------------------- program SysCall; function system(name : CString): integer; C; var result : integer; begin result := system ('ls -l'); writeln('system() call returned : ', result); end. --------------------------------------------------------- There may be other ways to do the same thing; you could declare a type `PChar' instead of `CString': type PChar = ^char; and replace all references to `CString' with `PChar'. Do *NOT* pass a "C" style string as a var-argument if the C prototype says `const char *' or you will get a coredump. You are right if you think this stuff belongs in a library, to be distributed with GPC. Have patience, or start coding! 5.0 GNU Pascal on the djgpp (MS-DOS) platform ********************************************* This chapter discusses some potential problems with GNU Pascal on MS-DOS, using djgpp. If you need more information ============================ GPC/djgpp is a djgpp V2 application, and most of the djgpp documentation applies for GPC too. A great source of information is the djgpp FAQ: http://www.delorie.com/djgpp/v2faq/faq202b.zip Another place to look for DJGPP documentation is the DJGPP Knowledge Base, at this URL: http://www.delorie.com/djgpp/doc/kb/ What do I download? =================== As discussed in section 2.2, other than GPC itself, you need an assembler, linker and friends, a C library and possibly a debugger. >From your local djgpp mirror, you can get these as: v2/djdev201.zip (C library) v2gnu/bnu270b.zip (assembler, ....) v2gnu/gdb416b.zip (debugger) The rest is up to you; `make' (v2gnu/mak375b.zip) can be useful, The latest RHIDE test release (an IDE with Borland-look) has support for GNU Pascal, and can be downloaded from: http://www.tu-chemnitz.de/~rho/rhidetest.html How do I install the compiler? ============================== If you don't have djgpp installed on your harddisk, create a directory for GNU pascal (`c:\gpc'), and unzip the archives. Make sure you preserve the directory structure (use `pkunzip -d'). Now, add the directory where `gpc.exe' lives (`c:\gpc\bin') to your path and set the DJGPP environment variable to point to your `djgpp.env' file: set DJGPP=c:\gpc\djgpp.env Then, add this to your `djgpp.env' file: --------------------------------------------------------- [gpc-cpp] C_INCLUDE_PATH=%/>;C_INCLUDE_PATH%%DJDIR%/lang/pascal;%DJDIR%/include;%DJDIR %/contrib/grx20/include [gpc] COMPILER_PATH=%/>;COMPILER_PATH%%DJDIR%/bin LIBRARY_PATH=%/>;LIBRARY_PATH%%DJDIR%/lib;%DJDIR%/contrib/grx20/lib --------------------------------------------------------- The binary distribution should come with a `djgpp.env' which is already modified, so you may not have to do this. The GPC online documentation is in GNU info format; you need the info reader (`txi390b.zip') to read it. To add the GPC documentation to the info directory file, edit the `c:\gpc\info\dir' file, and locate this section: --------------------------------------------------------- * GCC: (gcc.inf). The GNU C, C++, and Objective-C Compiler * GDB: (gdb.inf). The GNU Debugger (gdb and gdb-dpmi). --------------------------------------------------------- To add GPC, change it to look like this: --------------------------------------------------------- * GCC: (gcc.inf). The GNU C, C++, and Objective-C Compiler * GPC: (gpc.inf). The GNU Pascal Compiler * GDB: (gdb.inf). The GNU Debugger (gdb and gdb-dpmi). --------------------------------------------------------- Specific information for low-memory conditions and more can be found in the djgpp FAQ and documentation. I cannot read the info pages! ============================= To read the info pages, you need the `info' program from `txi390b.zip'. At least for some of the pre-releases of `gpc-1.2', the `gpc.info' file is invalid: it refers to the `gpc.i*' sections as `gpc.info-*'. This can be fixed by loading `gpc.inf' in an editor and replacing `gpc.info-*' with `gpc.i*' GPC says: no DPMI ================= You don't have a DPMI server installed, and DJGPP v2 requires it to run. You can either use one of the commercial DPMI servers (e.g., run `gpc' in a DOS box under Windows) or download and install CWSDPMI (`csdpmi3b.zip') which is a free DPMI server written for DJGPP. I have troubles with assembly code ================================== The GNU Assembler (`as.exe'), or `gas', called by GCC accepts "AT&T" syntax which is different from "Intel" syntax. Differences are discussed in section 17.1 of the djgpp FAQ. A guide is available which was written by Brennan Mr. Wacko Underwood <brennan(a)mack.rt66.com> and describes how to use inline assembly programming with DJGPP, at this URL: http://www.rt66.com/~brennan/djgpp/djgpp_asm.html Section 17.3 of the djgpp FAQ discusses some methods to convert "Intel" syntax to "AT&T". Tell me how to do DPMI, BIOS and other DOS related things. ========================================================== DPMI, BIOS and other functions are no different than other system functions. Refer to section 3.1 how to access your system's C-library. This small example shows how to use DPMI, copying some structures and function prototypes of `<dpmi.h>': --------------------------------------------------------- program dpmitest; {$X+} type word = __unsigned__ integer; short = __short__ integer; byte = __byte__ integer; type PDpmiVersionRet = ^TDpmiVersionRet; TDpmiVersionRet = record major : byte; minor : byte; flags : short; cpu : byte; master_pic : byte; slave_pic : byte; end; type PDpmiFreeMemInfo = ^TDpmiFreeMemInfo; TDpmiFreeMemInfo = record largest_available_free_block_in_bytes : word; maximum_unlocked_page_allocation_in_pages : word; maximum_locked_page_allocation_in_pages : word; linear_address_space_size_in_pages : word; total_number_of_unlocked_pages : word; total_number_of_free_pages : word; total_number_of_physical_pages : word; free_linear_address_space_in_pages : word; size_of_paging_file_partition_in_pages : word; reserved1 : byte; reserved2 : byte; reserved3 : byte; end; function DpmiGetVersion(ret: PDpmiVersionRet): integer; asmname '__dpmi_get_version'; function DpmiGetFreeMemoryInformation(info: PDpmiFreeMemInfo): integer; asmname '__dpmi_get_free_memory_information'; var version: TDpmiVersionRet; meminfo: TDpmiFreeMemInfo; begin DpmiGetVersion(@version); writeln('CPU type : ', version.cpu, '86'); writeln('DPMI major : ', version.major); writeln('DPMI minor : ', version.minor); DpmiGetFreeMemoryInformation(@meminfo); writeln('Free DPMI memory : ', meminfo.total_number_of_free_pages, ' pages.'); end. --------------------------------------------------------- I'm accessing an `array[1..4000000] of byte' and I got an exception. ==================================================================== Per default, the maximum stack size of a djgpp application is 256K. If you need more, you have to adjust it with the stubedit program, i.e.: stubedit your_app.exe minstack=5000K Still, it might be a good idea to use pointers for this kind of structures, and allocate the memory at runtime. 6.0 Getting Help **************** This section discusses ways to get help with GNU Pascal. Please read the documentation (info files, readme's) that come with GPC, plus other docs that might help (the djgpp FAQ if you use djgpp etc.) before you send email to the maintainers or mailing list. Help! The compiler crashed! =========================== If the compiler crashes, you have discovered a bug. A reliable compiler never crashes. To help the maintainers fix this bug, it is important that you send us a problem report. I think I found a bug - now what? ================================= Bugs are best reported to the GPC mailinglist <gpc(a)hut.fi>. That way, they always reach the maintainers. Try to give as much information as possible, plus a short code snippet that triggers the compiler bug. If you're on Unix, you can find out where the compiler crashed if you enable coredumps, then load the compiler (`gpc1') plus the core file in the debugger (`gdb /your_path_here/gpc1 core'), then type `backtrace' to get a stacktrace. Include this stacktrace in your bug report. Which newsgroup(s) are suited for GPC related problems? ======================================================= There are several Pascal related newsgroups, but none is dedicated just to GNU Pascal. This one may be useful: comp.lang.pascal.misc Pascal in general and ungrouped Pascals. Pascal syntax related questions may be appropriate in: comp.lang.pascal.ansi-iso Pascal according to ANSI and ISO standards. comp.lang.pascal.borland Borland Pascal questions. How to post to the mailing list =============================== You can send a message to the GPC mailing list by sending email to the list address <gpc(a)hut.fi> as if it were a person. How to become a subscriber to the mailing list ============================================== You can join the mailing list by sending a message to <gpc-request(a)hut.fi> (NOT <gpc(a)hut.fi> !) with your request to be added to the list. Maintenance is done by hand, so some delay is possible. How to unsubscribe from the mailing list ======================================== To leave the mailing list, send a message to <gpc-request(a)hut.fi>. 7.0 Miscellaneous ***************** I want to contribute; where do I start? ======================================= A list of jobs which should be done for GNU-Pascal can be found in the section "How to contribute" of the Texinfo deocumentation. In cases where somebody is already working on a topic, the name of that person is written behind the job's description. This does not mean that you shouldn't do that but just that you should get in contact with that person if you would like to contribute to that field. Where is the GNU Pascal FTP site? WWW? ====================================== The master FTP site for GNU Pascal is `kampi.hut.fi'. GNU Pascal related files can be found in: ftp://ftp.kampi.hut.fi/jtv/gnu-pascal/ This site is mirrored on: ftp://sunsite.doc.ic.ac.uk/gnu/pascal/ The latest developer releases can be downloaded from: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/ Also, we have a homepage on the web: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/ About this FAQ. =============== Original Maintainer: J.J. van der Heijden <j.j.vanderheijden(a)student.utwente.nl> Current Maintainer: Russ Whitaker <russwhit(a)mind.net> This is the second incarnation of the GNU Pascal FAQ list. Comments about, suggestions for, or corrections to this FAQ list are welcome. Please make sure to include in your mail the version number of the document to which your comments apply (you can find the version at the beginning of this FAQ list). Much of the info in, and inspiration for this FAQ list was taken from the gpc mailing list traffic, so you may have (unbeknownst to you) contributed to this list.

3 2

Binaries for Solaris 8
by Mariusz Zynel 01 Feb '00

01 Feb '00

Hi All Binaries for Solaris 8 (Sparc and Intel) are now available on: http://math.uwb.edu.pl/download/solaris8/ ftp://mizar.uwb.edu.pl/pub/misc/solaris8/ Hope someone uses it -- . Mariusz Zynel Institute of Mathematics | phone: +48 (85) 745 75 52 University of Bialystok | Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl 15-267 Bialystok | Poland | http://math.uwb.edu.pl/~mariusz/

2 1

Re: Compiling gpc-19991030 fails on rts.c
by Frank Heckenbach 24 Jan '00

24 Jan '00

J. David Bryan wrote: > On 21 Jan 00, at 9:58, Dr A Olowofoyeku wrote: > > > Your problem is probably due to things that are missing in the gcc Mingw > > libraries (and there are many of them). > > I have tracked my specific problem down to the lack of a "pwd.h" file in > Mingw (thanks, Chief!). The trouble is that "_p_pwl2c" in "rts.c" > references the "passwd" struct, which is defined in "pwd.h", but "pwd.h" > isn't part of Mingw. This is detected by the Pascal "configure", which > sets "#undef HAVE_PWD_H" in "rts-config.h" but is not covered by alternate > code in "rts.c". The result is a syntax error when compiling. As I said, the current code (to be released as a snapshot soon) contains such a check. However, no alternate code (just a failure result) -- if there's equivalent functionality on other systems (which I don't know about), I'll have to leave it to you to add it... 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

2 1

Jump to page:

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