September 1999 - Gpc

Script install-gpc-binary uploaded
by Frank Heckenbach 16 Sep '99

16 Sep '99

Hi, due to recent needs, I wrote a little script to simplify the installation of a GPC *binary* distribution into *another* directory than it was intended. To explain the situation: The gpc executable uses some files (e.g. the preprocessor gpc-cccp, the actual compiler gpc1 and the runtime library libgpc.a) which are usually stored in a directory <prefix>/lib/gcc-lib/<target>/<version>/. The <prefix>, i.e. the base directory for the GPC installation, can be specified while building GPC, and is then hard-coded into the gpc executable. When using gpc, it can be overridden with a `-B' option (for gpc-cccp and gpc1) and a `-L' option (for libgpc.a). The purpose of the install-gpc-binary script is just to create another script which calls gpc with those two options (in addition to any options given on the command-line). It examines the installed GPC binary distribution to find out the correct directories. The script created will be called gpc, and should be in the PATH, while the actual gpc executable should not be in the PATH, so calling `gpc' will invoke the script. Then, `gpc' can be used just like a gpc installed in the normal way, which is quite useful for using third-party Makefiles etc. Who needs this script? Those who get a binary distribution of GPC and don't install it into the right directory. These are usually not PC (including Linux) users, because most of them have root access and can install GPC into the right directory. There are also usually not system administrators of multi-user machines (who have root access and usually will prefer to build their software themselves, anyway). So, these are e.g. users on multi-user machines who can't convince their admins to install GPC for them, or just need it quickly, and/or don't have enough space in their home to build GPC... How to use it? - Get a GPC binary for your system, and the install-gpc-binary script. The script is available in the same FTP directories on agnes as the GPC binaries, i.e.: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/binary/install-gpc-binary ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/binary/install-gpc-binary - Unpack the GPC binary into any directory (but don't move it around after running the script). - Change into its "base" directory -- e.g. if the archive unpacks into usr/local/bin/..., usr/local/lib/..., etc. (below the current directory), change into usr/local, or move the contents of usr/local up to the current directory. In any case, the bin and lib directories should now be subdirectories of the current directory (the script will make sure this was done correctly). - Run this script and answer a few simple questions. - That's all. If you set your $PATH appropriately, you can now invoke `gpc' in the normal way. Frank -- Frank Heckenbach, frank(a)g-n-u.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Re: GPC on Solaris 2.6
by Frank Heckenbach 16 Sep '99

16 Sep '99

Tom Schneider wrote: > Thanks for the instructions on using patch (it's simple!) but I realized that > it is not good way to go because a version I provide to people would be > quickly out of date, or I would be forced to keep patching the latest version > (and eventually the patch would not work of course). I've put the patch into the official sources, but inactivated by `#if 0'. So, all you've got to do is activate the patch before compiling future GPC versions. If you want the compiler switch, you can either wait until we get around to it in our normal progress of work, or you can pay us (or any other programmer) to do it now. That's your option with free software... 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: Compiling GPC - mysteries
by Frank Heckenbach 16 Sep '99

16 Sep '99

Sorry, if two of my mails arrived twice. I had a head-crash, and after restoring my backups, those postings (which were apparently in the spool directory at the time of backup) came back... 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 - mysteries
by Frank Heckenbach 16 Sep '99

16 Sep '99

Hi, I hope you don't mind my reply to the list, but perhaps there are others who'd like a little insight into the Makefiles (or correct my mistakes)... The Chief wrote: > To make sure that I was not doing anything wrong, I downloaded the > latest GPC snapshot again, and extracted the files. I am a bit > confused by what I see in the directory tree: > > Directory of C:\cygnus\p > 03/08/99 08:10 23,724 Makefile.in > 1 File(s) 23,724 bytes > > Directory of C:\cygnus\p\rts > 20/06/99 20:11 3,674 Makefile.in > 1 File(s) 3,674 bytes > > Directory of C:\cygnus\p > 03/08/99 08:18 4,139 config-lang.in > 1 File(s) 4,139 bytes > > Directory of C:\cygnus\p\rts > 05/08/99 18:05 3,107 configure.in > 1 File(s) 3,107 bytes > > This shows that there are 2 different copies of 'Makefile.in' in the > GPC source tree. Which is the right one? Both of them. Actually, things are even more complicated. The main Makefile is created from Makefile.in and p/Make-lang.in (and possibly Make-lang.in's of other languages when installed). p/Makefile is created from p/Makefile.in. When you call make, you use Makefile. This does some work and at some time calls make with p/Makefile, calls p/rts/configure which creates p/rts/Makefile from p/rts/Makefile.in, and then calls make with p/rts/Makefile. Complicated, huh? configure.in, p/config-lang.in and p/rts/configure.in are used to create configure and p/rts/configure by the maintainers (with a utility called autoconf), so you don't normally execute them, but only configure, whereas p/rts/configure is called by Makefile (see above). > When I run 'configure' from > the 'rts' directory, everything works okay [...] That might be the problem, very probably indeed. You're not supposed to run configure in the p/rts directory because the Makefile does this and passes some appropriate parameters. In fact, after some recent changes of mine, it is now possible to run configure in p/rts manually -- but only if a current GPC is already installed, which is exactly not the case when building a new version of GPC... > If I copy the other 'Makefile.in' into the rts directory and run 'configure' > from there, a different makefile is generated, which contains > references to 'xgpc'. However, this makefile seems buggy. First, it > points to '../configure' - which doesn't exist. Second, if I copy > 'configure' to where it expects it, then any attempt to run 'make' > results in a message that I should invoke it from top level directory. You should not have to move files around. As described above, the Makefiles and configure scripts in the various directories are quite different ones and only work in their respective directories. > To compile GPC, copy or move `gpc/p' to become a subdirectory `p' > of the GCC source directory, `cd' to the GCC source directory, and > type > > ./configure > make CFLAGS="-g -O3" LANGUAGES=pascal > make CFLAGS="-g -O3" LANGUAGES=pascal install > > Well, this does not work, because 'configure' does not exist in the > GCC source directory. AFAICS it only exists in the 'p/rts' directory, No, it should be in the GCC source directory. If it doesn't, this explains why you ran the "wrong" configure, and probably explains the other problems, but why doesn't it exist? Which GCC sources did you get, the official gcc-2.8.1.tar.gz (or another version) from a GNU site, or from somewhere else? gcc-2.8.1.tar.gz contains one directory (gcc-2.8.1) which is the GCC source directory, and in this directory, there is a configure script. You can rename this directory to whatever you want, but the `p' directory must be a subdirectory of it. So to sum up: > 1. in which exact directory do I have to run 'configure'? In the GCC source directory, which is above the p directory. There must be a configure script there, otherwise something's wrong. You might want to try with the official GNU GCC sources... > 2. why are there 2 different copies of 'makefile.in' ? > 3. which is the correct one? See above. All of them, for different purposes. > 4. in which exact directory do I have to run 'make' ? In the GCC source directory, i.e. the same directory where you ran configure. > 5. Is the generated copy of 'Makefile' correct, or do I have to make > manual changes? You should not have to make any manual changes. However, you might need some additional makeflags (i.e. parameters on the make command line), e.g. (most likely) `exeext=.exe'. Also, you'll need a fairly complete set of GNU file, text and other utilities for the compilation and installation to succeed, including `ln' (in whatever way this might be realised, since MS-Windows does not support symbolic or hard links, AFAIK -- but if `ln' just copies, this would be sufficient here, except for increased disk space usage). Frank -- Frank Heckenbach, frank(a)g-n-u.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Re: GPC on Solaris 2.6
by Frank Heckenbach 16 Sep '99

16 Sep '99

Tom Schneider wrote: > Thanks Frank. Would the following modification just > leave the names alone properly? Yes, but it would leave them alone like the compiler stores them, i.e. first letter capitalized, the rest lower-case. That might not be what you want. It is planned to change this as soon as we've got the qualified identifiers working (before that, doing so would cause name space conflicts with libc). > Also, since I haven't gotten around to applying patches like this, > what would the command line be? Change into the right directory and do `patch < patchfile'. You might need GNU patch (haven't tried Solaris' patch, so I don't know if it works with unified diffs, but after my recent experiences with other Solaris tools, I doubt it...), and take care of the directory which is the most common source of problems with patch (note the `-p' option to patch). Afterwards, of course, recompile and reinstall. 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

4 8

Re: Compiling GPC - round 2
by Frank Heckenbach 16 Sep '99

16 Sep '99

"Dr A Olowofoyeku" wrote: > I now have the gcc sources for egcs-1.1.2 installed. I have run > 'configure' successfully. When I run 'make', I see that some EXEs > have been created in the 'gcc' subdirectory of the GCC source > directory - 'cpp.exe' and 'cccp.exe' (which both seem to be the same > file), That's right, that's just two different names for the same thing (`C Pre-Processor' and `C-Compatible Compiler Preprocessor'). Of course, on a real OS they are hard links to the same inode, so they don't waste disk space twice... > and some '.o' files have also been created there. However, I > finally get this output: > "make[1]: *** No rule to make target `pascal', needed by `native'. > Stop." > > Nothing at all seems to have happened in the 'p' subdirectory of the > GCC source directory. Now the questions: > > 1. Is egcs-1.1.2 okay for compiling GPC ? I think so. I never used EGCS, so, Peter, correct me if I'm wrong. > 2. If not, which version of GCC is okay? > 3. If egcs-1.1.2 is okay, then any suggestions as to what I am doing > wrong? I don't know. Have you: - unpacked GCC and GPC sources from the original archives (not influenced by "round 1") - moved the GPC sources into the right directory (so there is, say, gcc.c in the "main" directory, and gpc.c in a directory called p below it), - run configure in the "main" directory, - been asked if the GCC patch should be applied (or run patch before configure), - run something like `make LANGUAGES=pascal CFLAGS=-O2 exeext=.exe'? If you like, send me a log (your input and the output of the commands -- not the files created), and I'll check 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

1 0

Re: Compile gpc-19990118 on Solaris 2.7/7
by Frank Heckenbach 16 Sep '99

16 Sep '99

Kuang-Yu Liu wrote: > Hi, > > I have a novice question. According to p/diffs/gcc-2.8.1.diff parts 12, > 14, 16, files > > gcc-2.8.1/ansidecl.h > gcc-2.8.1/system.h > gcc-2.8.1/mbchar.c > > among other files, need to be patched. My question is my gcc 2.8.1 > source distribution does not have any of these files. I also checked > 2.5.8, 2.7.2.3, and 2.8.0. None of them has these three either. Where > can I find them? I got my gcc source distribution files straight from > GNU Mirror Sites. These files are created when patching. At least GNU patch does this automatically. If your version of patch doesn't, just create empty files of those names. > Trying to use binary distribution of gpc was not good either. I got > error message: > > module/unit interface `Gpc' could not be imported Please use the `--automake' option. 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: External names of GPC-compiled functions (was: GPC on Solaris 2.6)
by Frank Heckenbach 16 Sep '99

16 Sep '99

"Sergio A. Kessler" wrote: > >> >I was rather thinking of something like "MyProgram_MyFunction" > >> >or "MyUnit_MyFunction". When we introduce function overloading, > >> >additional suffixes indicating the parameter types can come up. > >> > >> "GPC_MyUnit_MyFunction" I think this will never choke with the linker... It will very easily. Just declare `int GPC_MyUnit_MyFunction;' in a C file and try to link it. What we should use IMHO is `MyUnit.MyFunction' (or any character instead of `.' that cannot occur in an identifier). Then, we can be sure that it doesn't cause problems (except perhaps with C++ which does its own name mangling, so we might have to look at it -- but it's quite different in different compilers and versions)-: ... > >I'd find it a little egocentric of GPC to name all user > >functions after himself ... ;-) > > I don't think so... GPC must say "this is my territory, don't bother me" > > I think is a clever namespace for GPC, well deserved. > egocentry of a _product_ is not bad ... That's a marketing question, and I don't disagree. ;-) However, as I said, anything only consisting of letters, numbers and underscores in a way is already C's "reserved" name space... 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

Compile gpc-19990118 on Solaris 2.7/7
by Kuang-Yu Liu 16 Sep '99

16 Sep '99

Hi, I have a novice question. According to p/diffs/gcc-2.8.1.diff parts 12, 14, 16, files gcc-2.8.1/ansidecl.h gcc-2.8.1/system.h gcc-2.8.1/mbchar.c among other files, need to be patched. My question is my gcc 2.8.1 source distribution does not have any of these files. I also checked 2.5.8, 2.7.2.3, and 2.8.0. None of them has these three either. Where can I find them? I got my gcc source distribution files straight from GNU Mirror Sites. Trying to use binary distribution of gpc was not good either. I got error message: module/unit interface `Gpc' could not be imported -- Regards, Kuang-Yu Liu liu(a)bacchus.wustl.edu

1 0

Compiling GPC - round 2
by Dr A Olowofoyeku 15 Sep '99

15 Sep '99

Hi all This is round 2. :-? I now have the gcc sources for egcs-1.1.2 installed. I have run 'configure' successfully. When I run 'make', I see that some EXEs have been created in the 'gcc' subdirectory of the GCC source directory - 'cpp.exe' and 'cccp.exe' (which both seem to be the same file), and some '.o' files have also been created there. However, I finally get this output: "make[1]: *** No rule to make target `pascal', needed by `native'. Stop." Nothing at all seems to have happened in the 'p' subdirectory of the GCC source directory. Now the questions: 1. Is egcs-1.1.2 okay for compiling GPC ? 2. If not, which version of GCC is okay? 3. If egcs-1.1.2 is okay, then any suggestions as to what I am doing wrong? Thanks. Best regards, The Chief -------- Dr. Abimbola A. Olowofoyeku (The African Chief) Email: laa12(a)keele.ac.uk Homepage: http://ourworld.compuserve.com/homepages/African_Chief/ Author of: Chief's Installer Pro v5.20a for Win32 ftp://ftp.demon.co.uk/pub/ibmpc/win95/apps/chief32/chief52a.zip

1 0