Gpc

gpc@gnu.de

5400 discussions

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 … [View More]

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 (… [View More]

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 … [View More]

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.… [View More]

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. … [View More]

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: > `… [View More]

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 -… [View More]-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. [View Less]

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 … [View More]

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