Gpc February 2014

gpc@gnu.de

8 participants
8 discussions

change SETGPC.BAT
by Jay Michael 25 Feb '14

25 Feb '14

SETGPC.BAT does not allow me to compile C using gpc: gpc tc.c -o tc As installed by dev_gnu_pascal-1.9.4.13.exe, SETGPC.BAT: set PATH=C:\prg\GPC\bin;%PATH% set C_INCLUDE_PATH=C:\prg\GPC\include set GCC_BASE=3.4.5 set GPC_EXEC_PREFIX=C:\prg\GPC\libexec\gcc\mingw32 set LIBRARY_PATH=C:\prg\GPC\lib;C:\prg\GPC\lib\gcc\mingw32\%GCC_BASE% set GPC_UNIT_PATH=C:\prg\GPC\lib\gcc\mingw32\%GCC_BASE%\units;C:\prg\GPC\units;C:\prg\GPC\units\winapi;C:\prg\GPC\units\objects;C:\prg\GPC\units\sysutils;C:\prg\GPC\units\objmingw I have been able to compile and link Pascal and C (one each) by only changing PATH. Separately, I succeeded by appending c:\prg\gpc\lib\gcc\mingw32\3.4.5\include to C_INCLUDE_PATH. (After running SETGPC.BAT) I don't know what to say is wrong. The lack of a trailing slash on GPC_EXEC_PREFIX results in a horrible mess in one of the attempted directories (C:/prg/GPC/libexec/gcc/mingw32mingw32/3.4.5/../../../../include/stddef.h) but appending a slash doesn't solve the real problem, because "libexec" is the wrong path to get to an include directory. Does GPC have different rules for the EXEC_PREFIX than GCC, so the lack of a trailing slash is not a mistake for GPC_EXEC_PREFIX? Does the setting of all of the variables other than PATH date back to a time before GPC did such an elaborate job of fabricating directory names? Or before GPC had the target and version wired in? Is it likely that all I need is to prepend GPC/bin to PATH? Or do you think I will need some of the other environment variables when I get around to trying to compile more substantial programs?

1 0

Compiling GPC on Msys
by Kevan Hashemi 21 Feb '14

21 Feb '14

Greetings, I'm trying to compile GPC from sources on Msys, within mingw on 32-bit Windows 7. Is this possible? The gcc-3.4.6/configure appears to work. It patches the GCC 3.4.6 for Pascal. I run the makefile, which proceeds for a while, with warnings like this: warning: structure 'reg_info_def' used but not defined Then the compile then fails with: cc1.exe: error: min-insn-modes.c: Invalid argument If any of this is familiar, or if I'm missing something obvious, please let me know. Ultimately, I'd like to be in a position to fix the GetMicroSecondTime routine, which does not work in Windows, and has not done so for years. Yours, Kevan -- Kevan Hashemi, Electrical Engineer Physics Department, Brandeis University http://alignment.hep.brandeis.edu/

2 1

Change Include in frontend
by Rajat Singh 15 Feb '14

15 Feb '14

Hi, I want to include the files using #include <filename> in GNU PASCAL instead of {$INCLUDE}. I am unable to trace where the changes has to happen. Thanks for help in advance. Regards, Rajat Singh

2 1

GNU PASCAL FRONT END Changes to mimic HP PASCAL m68k
by Kavitha Manjunath 15 Feb '14

15 Feb '14

Dear Team, Greeting for the day. I am a student working on GNU PASCAL Porting to adapt a version of HP PASCAL m68k for school purposes. I was trying to do the following on which I am stuck. Can you please provide me some insight and lead a path to achieve the same. Thanks a million in advance 1. I want to include the files using #include <filename> instead of {$INCLUDE}. I am unable to trace where the changes has to happen. Also all the directives in the similar way without the use of "{}". Request your help. Thanks once again. Regards Kavitha

1 0

Integer Size on 64-Bit
by Kevan Hashemi 14 Feb '14

14 Feb '14

Greetings, On Red Hat Linux 6.5 running on a 32-bit machine, I compile GPC to obtain a 32-bit Pascal compiler in which the integer type is 4 bytes long. I compile TclTk from sources and obtain an executable in which the C "int" type is 32 bits long. They work well together. On Red Hat Linux 6.5 running on a 64-bit machine, I compile GPC to obtain a 64-bit Pascal compiler in which the integer type is 8 bytes long. I compile TclTk from sources and obtain an executable in which the C "int" type is still 32 bits long. They do not work well together. I can edit my Pascal code to make all integer types a fixed length regardless of architecture. But I was wondering if there is a Pascal compiler directive that I can use to force the integer size to 32 bits on all platforms. Or perhaps there is a configure option when I compile GPC from its sources that will tell the compiler to make the integer type 32 bits. Yours, Kevan -- Kevan Hashemi, Electrical Engineer Physics Department, Brandeis University http://alignment.hep.brandeis.edu/

2 1

Compiling for Shared Libraries
by Kevan Hashemi 06 Feb '14

06 Feb '14

Dear GPC Users, I just compiled GPC from sources on both 32-bit and 64-bit Linux machines. On both machines, I'm running Scientific Linux 6.4, a derivative of Red Had Linux 6.4. The local C compiler is 4.4.7 in both cases. On the 32-bit machine, I can compile from Pascal to make objects, and link them with libgpc.a to make a shared library. But on the 64-bit machine I find that I must pass -fPIC to GPC to force it to compile position-independent code for the subsequent link. Even then, libgpc.a is position-dependent, so I can't link it into a shared library. So I edit the GPC build's Makefile: CFLAGS = -g -O2 -fPIC Now I build GPC again and re-install. The new libgpc.a is position-independent, and I can make my shared library. Does anyone know why the default on 64-bit is position-dependent, while on 32-bit it is position-independent? Is there an easier way to add a compiler option to the build process, other than editing the Makefile produced by the GCC_3.4.6 configure script? (For example, can I pass a compiler option into the configure script or into the makefile.) Anyway: I have adapted my compiler GPC instructions below, and I'll be adding more Linux binary install files in the coming weeks. http://alignment.hep.brandeis.edu/Software/Pascal/Index.html Yours, Kevan -- Kevan Hashemi, Electrical Engineer Physics Department, Brandeis University http://alignment.hep.brandeis.edu/

3 3

GNU frontend modification
by Rajat Singh 03 Feb '14

03 Feb '14

Hi All, Greetings for the day !! I am trying to modify the GNU Pascal fronted. I have gone through GNU Pascal manual and GNU Pascal internals site and this is what I have understood. 1.Lexer - I need to modify pascal-lex.l file and using flex compile it to lex.yy.c file.Rename this file to pascal-lex.c 2. Parser - I need to modify parse.y file and using bison compile it to parse.c file. Now what I am supposed to do next, to make these changes reflect when I compile a pascal file ? Thanks a lot in advance. Thanks and regards, Rajat

2 1

gpc compiler failed on Mac OS X 10.9.1
by Thomas Schneider 03 Feb '14

03 Feb '14

I have Mac OS X 10.9.1 Maveric. Pacal programs compile but fail to run: % cat tst.p program h(output); begin writeln(output,'did'); end. % tst dyld: no valid entry point Trace/BPT trap but a previously compiles version does run: % tst2009 did http://www.microbizz.nl/gpc.html There I find: GNU Pascal 3.4.6u4 installer for Mac OS X 10.6 Intel native and PowerPC cross-compiler15.7 MB) The file gpc346u4-10.6-Intel.dmg is identical (by diff) with the one I already have installed. So what's wrong? How do I get it to compile correctly? Tom Thomas D. Schneider, Ph.D. Senior Investigator National Institutes of Health National Cancer Institute Center for Cancer Research Gene Regulation and Chromosome Biology Laboratory Molecular Information Theory Group Frederick, Maryland 21702-1201 schneidt(a)mail.nih.gov http://schneider.ncifcrf.gov/ (current link) http://alum.mit.edu/www/toms (permanent link)

3 11

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 February 2014