- Gpc - gnu.de

gpc almost complied - now what?
by toms＠ncifcrf.gov 19 Apr '02

19 Apr '02

Hi Folks! I got the latest packages and tried to install on a BSD system my ISP just set up (4.5-RELEASE FreeBSD 4.5-RELEASE). It went pretty well. Following are the things I did (approximately) ending on an error message that I can't interpret. What's next? wget http://www.gnu-pascal.de/current/gcc-core-2.95.2.tar.gz gunzip gcc-core-2.95.2.tar.gz tar xvf gcc-core-2.95.2.tar wget http://www.gnu-pascal.de/current/gpc-20020410.tar.gz gunzip gpc-20020410.tar.gz tar xvf gpc-20020410.tar cd gpc-20020410 mv p ../gcc-2.95.2/gcc mkdir gpc-build cd gpc-build/ /users/tds/gpc/gcc-2.95.2/configure --enable-languages=pascal This seems to have worked fine. make ******************************** (lots of compile messages) xgpc: xgpc:: No such file or directory xgpc: :: No such file or directory xgpc: No: No such file or directory xgpc: such: No such file or directory xgpc: file: No such file or directory xgpc: or: No such file or directory xgpc: directory: No such file or directory xgpc: xgpc:: No such file or directory xgpc: No: No such file or directory xgpc: input: No such file or directory xgpc: files: No such file or directory *** Error code 1 Stop in /users/tds/gpc/gpc-build/gcc/p/rts. *** Error code 1 Stop in /users/tds/gpc/gpc-build/gcc. *** Error code 1 Stop in /users/tds/gpc/gpc-build. ******************************** 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/

5 7

Accessing Memory
by Rocker73＠aol.com 19 Apr '02

19 Apr '02

Hello, I have a question about accessing memory using GPC. I'm running GPC on a FreeBSD UNIX system. How do you directly access memory via a generic pointer in GPC? In Borlan Pascal 7, there are special array called Mem, MemW, and MemL. Does GPC have anything equivilent? Dan.

3 2

GPC 2.1 RC 6 released
by Frank Heckenbach 18 Apr '02

18 Apr '02

Hi everyone, GPC version 20020410, the release candidate #6 for GPC 2.1, has been uploaded to http://www.gnu-pascal.de/current/gpc-20020410.tar.gz A diff against RC 5 can be found at http://www.gnu-pascal.de/current/gpc-20020402-20020410.diff.gz According to a request by the Chief, the install target `pascal.install' and the Pascal only binary distributions (`pascal.bindist') do not include libgcc.a anymore. It is now only included with `pascal.install-with-gcc' and Pascal binaries with gcc (`pascal.bindist-with-gcc'), since the former should be used if (and only if) a matching GCC version is already installed which includes libgcc.a. A module name conflict (which prohibited certain module names, e.g., `Files') was resolved, thanks to a report by Carel Fellinger. In the course of fixing this problem, the directive `asmname' was enabled for programs, units and module interfaces. Some small bugs were fixed, including a problem when building GPC with `-pipe' (thanks to a report by George Shapovalov), the problem that ParamStr was not accepted as the first argument of `ReadStr' and `Val' (thanks to a report by Maurice Lombardi), a bug with differences of integer constans and a bug with a special case of nested schema types (thanks to reports by Emil Jerabek) and some other small bugs. 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

3 5

Re: gpc almost complied - now what?
by Ernst-Ludwig Bohnen 17 Apr '02

17 Apr '02

On Wed, 17 Apr 2002, da Silva, Joe wrote: > Hi Ernst-Ludwig, > > I'm new to Linux, but my experience with learning *nix, is that the > safest "help" option to attempt with an unfamiliar program or script > is '--help'. So as a suggestion, if it's not difficult, you should also > detect a '--help' argument as equivalent to '-h'. > Regards, > Joe. OK, done. By the way, the script should not start working immediately after typing it's name, instead it should print some help. Change is under way. Regards, Ernst-Ludwig

1 0

editor contribution
by Russell Whitaker 17 Apr '02

17 Apr '02

Hi Attached is a tar.gz source listing of an editor written in pascal. Caution: It works just fine here ( linux box ) but it might not in yours - so approach with caution. enjoy Russ

3 4

Re: gpc ebuild for gentoo linux
by da Silva, Joe 17 Apr '02

17 Apr '02

Thanks again. Please see below ... Joe. > -----Original Message----- > From: Prof. A Olowofoyeku (The African Chief) > [SMTP:african_chief@bigfoot.com] > Sent: Thursday, April 11, 2002 8:27 PM > To: da Silva, Joe > Subject: RE: gpc ebuild for gentoo linux > > On 11 Apr 2002 at 19:38, da Silva, Joe wrote: > > > Thanks, Chief. > > > > Mandrake normally has GCC 2.96 (well, my copy at least), > > Yes, it does. But v8.1 only comes with gcc-3.0.x, but that is not the > default compiler that the system uses. > > > which from previous discussions is a "broken" version. > > I don't think it is broken in respect of what it can do (it can build > the linux kernel, and anything else). But the sources are probably > not compatible with building GPC on them. > > > So my plan to eventually > > install a GCC 2.95.3 and a similar build of GPC might be problematic? > > Not at all. I have done that. It is quite straightforward. However, > you will need to install GPC with "make install", rather than > "make pascal.install". That way, gcc-2.95.3 will also be installed > along with GPC. Just make sure that you don't overwrite the existing > gcc installation. I normally configure with "--prefix=/usr/local", so > [Joe da Silva] Is there any particular reason I should not overwrite an existing GCC installation? I had intended to use "make install" and standardize on 2.95.3 for both GCC and GPC (I'd rather not have two versions of GCC installed, unless I have to). > that the new installation goes to a different place from the system > compiler, and when I want to run GPC, I first do: > "export PATH=/usr/local/bin:$PATH > This means that the GPC path will be found first, and if GPC needs to > use the C compiler for something (e.g., building the crt unit), it > will use the new gcc-2.95.3 instead of the system gcc compiler). > > > Hmmm ... looks like I will have to become a lot more familiar with > > this Linux stuff, before I try this. :-/ > > There is nothing to fear. It is all quite straightforward. It is as > simple as: > configure --prefix=/usr/local > make > make install > export PATH=/usr/local/bin:$PATH > > Best regards, The Chief > --------- > Prof. Abimbola Olowofoyeku (The African Chief) > Email: African_Chief(a)bigfoot.com > http://www.bigfoot.com/~african_chief/

3 2

None
by Adam Naumowicz 17 Apr '02

17 Apr '02

Hello, A quick question - what can be wrong: after installing the newest GPC I still get the same error: /usr/lib/crt1.o: In function `_start': /usr/lib/crt1.o(.text+0x18): undefined reference to `main' collect2: ld returned 1 exit status while compiling simple: unit blah; interface implementation end. Is there something wrong with the installation ? (previously I had gcc 2.95.3 installed in /usr/lib, I compiled and installed GPC (by make install) into /usr/local/). Thanks for any hints. Best Regards, Adam Naumowicz -------------------------------------- WWW: http://math.uwb.edu.pl/~adamn/ --------------------------------------

4 5

Re: GPC && ( BeOS || mac os x )
by Prof. A Olowofoyeku (The African Chief) 16 Apr '02

16 Apr '02

Hi [...] > I am including the output, but only the last 7 or 8 lines, since the > rest seems okay: > > gcc -c -DIN_GCC -g -O2 -DHAVE_CONFIG_H -I. > -I/boot/home/fred/fsf/gcc/gcc -I/boot/home/fred/fsf/gcc/gcc/config > -I/boot/home/fred/fsf/gcc/gcc/../include > /boot/home/fred/fsf/gcc/gcc/config/i386/winnt.c > /boot/home/fred/fsf/gcc/gcc/config/i386/winnt.c: In function > `i386_pe_dllimport_p': > /boot/home/fred/fsf/gcc/gcc/config/i386/winnt.c:201: > `TARGET_NOP_FUN_DLLIMPORT' undeclared (first use in this function) > /boot/home/fred/fsf/gcc/gcc/config/i386/winnt.c:201: (Each undeclared > identifier is reported only once > /boot/home/fred/fsf/gcc/gcc/config/i386/winnt.c:201: for each function > it appears in.) make[1]: *** [winnt.o] Error 1 make[1]: Leaving > directory `/boot/home/buildarena/gcc' make: *** [all-gcc] Error 2 > > What I need to know is what flags I need to use with 'configure' > and/or 'make' to specify that I don't want anything related to Windows > compiled in. Isn't this possible? That would effectively skip right > over these headers and source files, right? Perhaps. Basically, gcc cannot compile itself. This makes it a gcc matter and not a GPC matter - but the prospects are not looking very bright at the moment. I think you need to speak to BeOS gcc porters about this, since no-one here will have a clue as to what the real probem is. I am surprised that the BeOS gcc porters didn't provide gcc sources that will compile without any need for tinkering. What is their advice concerning the configure scripts and the build process? Do they build gcc natively, or do they use a cross compiler? Obviously, 'configure', when left to its own devices, thinks that you are using Windows. This may be due to the deliberate actions of the porters, or 'configure' may just have guessed wrongly. Try running 'config.guess' and see what system it thinks you are running on. You may need to supply other arguments to 'configure' (e.g., '--build', '--host', '--target'). Best regards, The Chief --------- Prof. Abimbola Olowofoyeku (The African Chief) Email: African_Chief(a)bigfoot.com http://www.bigfoot.com/~african_chief/

1 0

GPC && ( BeOS || mac os x )
by Philip George 16 Apr '02

16 Apr '02

Chief, your suggestion was brilliant in its simplicity. I found two places that prepare gcc for BeOS: [1] http://www.geekgadgets.org [2] http://www.toyoshima-house.net I had a little luck with the latter, but not enough to complete the task. GeekGadgets provides all the source for gcc 2.95.1, but all the necessary changes were made to accommodate installation on BeOS. So, configuration now works perfectly: % cd ~/buildarea % make distclean % /..../configure --enable-languages=pascal --prefix=/boot/testloc Needless to say, this gave way to much whooping and hollering! :) --BUT-- (the inevitable 'BUT') Here is the problem I'm having now, and I'm POSITIVE that it's a simple one to resolve. I just can't quite get my brain around it: When I run 'make' after a successful configuration, it churns on it for about 5 minutes, spitting out the usual DHAVE_THIS and DHAVE_THAT, looking for the most part like a successful compilation in the works.... BUT... all of a sudden the whole thing comes to a screeching halt at: make[1]: *** [winnt.o] Error 1 make[1]: Leaving directory `/boot/home/buildarea/gcc' make: *** [all-gcc] Error 2 % I am including the output, but only the last 7 or 8 lines, since the rest seems okay: gcc -c -DIN_GCC -g -O2 -DHAVE_CONFIG_H -I. -I/boot/home/fred/fsf/gcc/gcc -I/boot/home/fred/fsf/gcc/gcc/config -I/boot/home/fred/fsf/gcc/gcc/../include /boot/home/fred/fsf/gcc/gcc/config/i386/winnt.c /boot/home/fred/fsf/gcc/gcc/config/i386/winnt.c: In function `i386_pe_dllimport_p': /boot/home/fred/fsf/gcc/gcc/config/i386/winnt.c:201: `TARGET_NOP_FUN_DLLIMPORT' undeclared (first use in this function) /boot/home/fred/fsf/gcc/gcc/config/i386/winnt.c:201: (Each undeclared identifier is reported only once /boot/home/fred/fsf/gcc/gcc/config/i386/winnt.c:201: for each function it appears in.) make[1]: *** [winnt.o] Error 1 make[1]: Leaving directory `/boot/home/buildarena/gcc' make: *** [all-gcc] Error 2 What I need to know is what flags I need to use with 'configure' and/or 'make' to specify that I don't want anything related to Windows compiled in. Isn't this possible? That would effectively skip right over these headers and source files, right? Again, thanks in advance for any/all assistance. - pgeorge >> There are a couple threads about installing GPC onto Mac OS X and BeOS. >> The main one for BeOS ends with "just try it," which I did... and it >> didn't work. > [...] >> • The failure is the same on both platforms when running 'configure' >> - 'Configuration i586-pc-beos not supported' (BeOS) >> - 'Configuration powerpc-apple-bsd not supported' (Mac OS X) > > You may be able to solve this by amending the various configure.* > scripts, first, to remove the error being reported, and secondly, to > tell them what to do with BeOS and Mac OSX. You will find various > sections and entries which relate to the various platforms supported by > gcc (try searching for "linux" in the various "configure.in" scripts, > and you will see what I mean). Since you are writing an OS under BeOS, > you obviously know a lot about the system internals. You should be able > to supply the scripts with entries for BeOS. > >> I'm using GCC 2.95.2 source and GPC 20020417 (tried ...410 also) from >> which to attempt the builds and I'm cleaning between failed >> attempts. I >> am following the installation instructions to the T, right down to the >> folder called 'fred'. >> >> For those who are wondering, BeOS 5 is about 99% POSIX compliant (the >> other 1% is GUI-related I believe). Maybe that's the hitch; is there >> possibly a --posix flag or something like that??? HHHmmmmm.... Not >> sure. It's primary language is C/C++ and the default tools are gnu gcc >> and the rest of the gang, so one would thing that we could slide GPC >> right in there beside it without a problem. >> > > If you can build gcc under BeOS, then you are on your way. If gcc is > the default tool, then someone has obviously been able to build gcc. My > advice is - find that someone and ask them how they did it. It is > necessary for building GPC that gcc can be built on the system. > Presumably, whoever built the gcc compilers for BeOS have (under the > GPL) to make their gcc sources available. Use those sources instead of > the pristine GNU sources, and you may well have greater success. > > PS: it may well be that the GPC patches will fail under a patched gcc > version (if there had been too many changes), but I doubt that they > will fail.

1 0

GPC && ( BeOS || mac os x )
by Philip George 15 Apr '02

15 Apr '02

There are a couple threads about installing GPC onto Mac OS X and BeOS. The main one for BeOS ends with "just try it," which I did... and it didn't work. The most helpful one for Mac OS X links to a PDF that contains instructions for getting GPC compiled... but it's in French, and after the free French-English translation websites butcher it, it's more difficult to read than it was in French! Here's the deal: • I need to install GPC on BeOS 5 for Intel - Getting it installed in Mac OS X is secondary at best . BUT, it would be a nice bonus if you could help . I would like the focus of this thread to be on BeoS • I'm writing a new operating system from within BeOS - I am writing custom link libraries specific to my OS . So I don't care about lack of BeOS-specific libs in GPC • BePascal is no more, so it is not an option - Unless you know where I can still obtain it from • The failure is the same on both platforms when running 'configure' - 'Configuration i586-pc-beos not supported' (BeOS) - 'Configuration powerpc-apple-bsd not supported' (Mac OS X) I'm using GCC 2.95.2 source and GPC 20020417 (tried ...410 also) from which to attempt the builds and I'm cleaning between failed attempts. I am following the installation instructions to the T, right down to the folder called 'fred'. For those who are wondering, BeOS 5 is about 99% POSIX compliant (the other 1% is GUI-related I believe). Maybe that's the hitch; is there possibly a --posix flag or something like that??? HHHmmmmm.... Not sure. It's primary language is C/C++ and the default tools are gnu gcc and the rest of the gang, so one would thing that we could slide GPC right in there beside it without a problem. I've never had good experiences with mailing lists. People tend to get off topic or are unable to see THE BIG PICTURE sometimes, but I've seen some quality threads on this particular list, so I'm hopeful that a solution is right around the bend. Thanks in advance for any/all assistance. - pgeorge

2 1