Re: GNU Pascal is still kind of alive
"Prof Abimbola Olowofoyeku" <[email protected]> Tue, 10 Jan 2017 16:18:47 -0000
| Newsgroups | gmane.comp.compilers.gpc |
|---|---|
| Organization | ChiefSoft |
| Message-ID | <[email protected]> |
On 10 Jan 2017 at 10:52, Kevan Hashemi wrote: > Dear Chief, > > > Is there anyone else out there? > > I can hire a computer science student for the summer to work on GPC, but > I don't think they will be capable of doing much with the migration to > newer versions of GCC. They may be able to help with other projects. That sounds promising! [...] > If we can be sure of compiling GCC 3.4.6 on Windows, Linux, and MacOS > using whatever version of GCC is current for those platforms, then I > think we should be okay. I'm confident we can do so on Windows 32-bit, > Linux 32-bit and Linux 64-bit. I can't compile GCC 3.4.6 on Windows > 64-bit I believe because of divergeance between MinGW 64-bit and MinGW > 32-bit. On MacOS I can't compile GCC 3.4.6. It took me some time to get > GPC to run on MacOS 10.7.5, but I just posted my notes on how to do > that. > > http://alignment.hep.brandeis.edu/Software/Pascal/Pascal.html#Notes > > We (my group) is going to try to get the same MacOS GPC binaries working > on MacOS 10.9 and later. I have not tried to build on the current gcc version for my Linux box - I just carry with me my binary gpc tarball built on 4.1.2, with its own statically linked gcc-4.1.2 environment (which can build gpc without fuss). This has served my needs regardless of which Linux version I happen to be using (and I have quite a few different Linux VMs). Perhaps such a complete gcc build environment from an earlier MacOS could be used as a last resort? Or perhaps you are keen to use the latest and best features of the current MacOS compiler? (I personally just need a gpc that runs and compiles my programs correctly). > > Mac OSX seems to have major issues here, but it is probably nothing > > that cannot be solved by; [a] suitably amending the gpc driver program > > (gpc.c) to pass on any needed arguments, or [b] by writing a custom > > collect2.c to replace the default collect2.c, and compiling it > > separately, or [c] by writing your own os-hacks.h and putting in the > > include directory. > > Okay. We will look into that here. > > > If anyone is interested, I have samples of [a], [b] and [c] > > I have your os-hacks.h file. Is there more? If so, then yes I'm > interested. Will send that by private email (unless someone on this list is desperate to see C source code). Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/ _______________________________________________ Gpc mailing list [email protected] https://www.g-n-u.de/mailman/listinfo/gpc