Gpc October 1998

gpc@gnu.de

24 participants
42 discussions

[Q] about error message...
by wrkim 16 Oct '98

16 Oct '98

Hi. After install GPC(GNU Pascal Compiler), When run gpc, I get error message . My system environment is sparc-solaris-2.5.1 and gcc-2.7.2.1. Error message :: gpc:Internal compiler error:program gpc-cpp got fatal signal 4 ************************************************************************* Dongguk Uni. Computer Science Email :: wrkim(a)wonhyo.dongguk.ac.kr Name :: Kim Mi Young Homepage::http://wwwcs.dongguk.ac.kr/~wrkim *************************************************************************

2 1

Help: make
by dang hai 15 Oct '98

15 Oct '98

Would you help me with the error below. Thanks in advance Minh sh ./move-if-change tmp-gpc-parse.h ./gpc-parse.h ./gpc-parse.h is unchanged cc -c -DGPC -DIN_GCC -g -I. -I. -I../gcc-2.7.2.1 -I../gcc-2.7.2.1 -I../gcc-2. 7.2.1/config gpc-parse.c cc -c -DGPC -DIN_GCC -g -I. -I. -I../gcc-2.7.2.1 -I../gcc-2.7.2.1 -I../gcc-2. 7.2.1/config gpc-decl.c cc: Error: gpc-decl.c, line 2962: In this statement, "((enum tree_code)(((tail)- >list.value))->common.code)" is not an lvalue, but occurs in a context that requ ires one. TREE_CODE (TREE_VALUE (tail)) = code; ----------------^ make: *** [gpc-decl.o] Error 1 ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

2 1

Help: make
by dang hai 15 Oct '98

15 Oct '98

1 0

Configure problem
by minh.h.cao＠boeing.com 14 Oct '98

14 Oct '98

Hi, When I run make to build pascal 2.0, I get the following error. Would you help me on this ? Thanks in advance. cc -DGPC -DIN_GCC -g -o gpc gcc.o gpc-version.o ../gcc-2.7.2.1/obstack.o `if [ -f "../gcc-2.7.2.1/alloca.o" ]; then echo "../gcc-2.7.2.1/alloca.o" ; else true ; fi` `if [ -f "../gcc-2.7.2.1/mall.c cc: Error: gpc-decl.c, line 2962: In this statement, "((enum tree_code)(((tail)->list.value))->common.code)" is not an lvalue, but occurs in a context that requires one. TREE_CODE (TREE_VALUE (tail)) = code; ----------------^ *** Exit 1 Stop. ----------------------------------------------------------------------- Another thing I see when run ./configure is not the same with a example from install note. Compiler for GPC: cc My showing cc not gcc. Is this a problem ? -------------------------------------------------------------------------- Configuration summary: Building a native alpha-dec-osf4.0 compiler GPC sources in: . GCC sources in: ../gcc-2.7.2.1 GCC object code in: ../gcc-2.7.2.1 GCC version: 2.7.2.1 Compiler for GPC: cc Compiler for libgpc.a: ../gcc-2.7.2.1/xgcc -B../gcc-2.7.2.1/ Compiler flags: -g Installation path: /usr/local/bin, /usr/local/lib/gcc-lib/alpha-dec-osf4.0/2.7.2.1 -------------------------------------------------------------------------- Now, type "make" to build the compiler and runtime system.

2 1

Re: External references
by Frank Heckenbach 14 Oct '98

14 Oct '98

Peter Gerwinski wrote: > > Yes, I think that's this problem. If you compile a unit with `-S', > > you'll find that global variables in the implementation > > ... where it _must_ be like this ... (* Why? *) > > (as well as global variables in a program) > > ... where we should discuss about ... > > > are `local' instead of `global' or `comm'. > > Global variables of the program must be in the data (and not in > the stack) segment in order to circumvent limitations of the > stack size. Normally, there is no need to make them visible to > the linker because programs cannot be "used" (imported) by > other Pascal programs, modules, or units. (In C, such > variables are declared `static'.) > > If you want to make a global variable of the program visible to > the linker (and thus to external assembler routines), you can > use the following trick: > > Program Test; > > Var > Foo: external Integer; > Foo: Integer; > > begin > end. > > This produces a `comm' variable without `local'. > > The first declaration of `Foo' tells the compiler that there > is some external integer variable `Foo'. The second one > allocates storage for this variable, remembering that it must > be accessible from the external world. > > Okay like this? I think so, for the following reason: when GPC will get qualified identifiers and/or function overloading, the translation Pascal identifier -> asmname can't be as simple as it is now. Therefore, it's not wrong to get used to do special declarations for variables one wants to use externally. What I find strange is the `external' in the example and having to repeat the declaration -- though I understand why it is currently necessary. I think in the long run, we should think of a better syntax for that. Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

unresolved references in libgpc.a
by Bernd Kurzan E1 14 Oct '98

14 Oct '98

Hello! After applying the new patch to the gcc-2.8.1 source code the gpc-19980830 compiler is now built by gcc-2.8.1 without any errors. When compiling the Pascal-programs in the "test" directory, however, most of the programs cannot be correctly compiled by gpc, because there are apparently some unresolved references in libgpc.a (see below an excerpt from the screen!). Is there a parameter file missing? Bernd =============================== typical error messages: /usr/lib/gcc-lib/i586-pc-linux-gnulibc1/2.8.1/libgpc.a(write.o): In function `_p_write': /usr/local/src/gcc-2.8.1/p/rts/wrtinc.c:123: undefined reference to `_p_strlen' /usr/local/src/gcc-2.8.1/p/rts/wrtinc.c:124: undefined reference to `_p_strlen' /usr/local/src/gcc-2.8.1/p/rts/wrtinc.c:138: undefined reference to `_p_strlen' /usr/lib/gcc-lib/i586-pc-linux-gnulibc1/2.8.1/libgpc.a(file.o): In function `_p_nameit': /usr/local/src/gcc-2.8.1/p/rts/file.c:204: undefined reference to `_p_strlen' /usr/local/src/gcc-2.8.1/p/rts/file.c:218: undefined reference to `_p_strlen' /usr/lib/gcc-lib/i586-pc-linux-gnulibc1/2.8.1/libgpc.a(rtsstr.o): In function `Upcasestring': /usr/local/src/gcc-2.8.1/p/rts/rtsstr.pas:109: undefined reference to `_p_gpc_upcase' /usr/lib/gcc-lib/i586-pc-linux-gnulibc1/2.8.1/libgpc.a(rtsstr.o): In function `Locasestring': /usr/local/src/gcc-2.8.1/p/rts/rtsstr.pas:115: undefined reference to `_p_gpc_locase' /usr/lib/gcc-lib/i586-pc-linux-gnulibc1/2.8.1/libgpc.a(rtsstr.o): In function `Strdup': /usr/local/src/gcc-2.8.1/p/rts/rtsstr.pas:206: undefined reference to `_p_strlen' /usr/lib/gcc-lib/i586-pc-linux-gnulibc1/2.8.1/libgpc.a(string.o): In function `_p_writestr': /usr/local/src/gcc-2.8.1/p/rts/wrtinc.c:123: undefined reference to `_p_strlen' /usr/local/src/gcc-2.8.1/p/rts/wrtinc.c:124: undefined reference to `_p_strlen' /usr/local/src/gcc-2.8.1/p/rts/wrtinc.c:138: undefined reference to `_p_strlen' /usr/lib/gcc-lib/i586-pc-linux-gnulibc1/2.8.1/libgpc.a(string.o): In function `_p_readstr': /usr/local/src/gcc-2.8.1/p/rts/string.c:521: undefined reference to `_p_strlen' =========================================

2 1

Re: External references (Was: Code Gen Prob -- Retraction...)...
by Frank Heckenbach 13 Oct '98

13 Oct '98

Orlando Llanes wrote: > On Mon, 12 Oct 1998, Frank Heckenbach wrote: > > This seems to be a bug in fact. They are declared "local" in the > > assembler output (or shouldn't they be global for some reason, Peter?). > > I meant at a low level within the unit. In my example, a variable was > declared in the unit, and another variable declared in the asm file. The > unit had access to the asm's variables, but not vice versa. Yes, I think that's this problem. If you compile a unit with `-S', you'll find that global variables in the implementation (as well as global variables in a program) are `local' instead of `global' or `comm'. -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

2 1

Re: argc/argv?
by Frank Heckenbach 13 Oct '98

13 Oct '98

Jo Dillon wrote: > Just a quick question - how do I get access to command-line parameters > from gpc? (I.e. the equivalent of main(argc,argv)) I looked through the info > documentation and couldn't find anything. ParamCount and ParamStr(n). Note, ParamCount does not include the 0th argument (program name), unlike argc. (However, ParamStr(0) does return it.) You are using a newer GPC than 2.0, aren't you? (2.0 did not have those functions. They were added sometime in 1997.) Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

argc/argv?
by Jo Dillon 13 Oct '98

13 Oct '98

Just a quick question - how do I get access to command-line parameters from gpc? (I.e. the equivalent of main(argc,argv)) I looked through the info documentation and couldn't find anything. -- Jo Harmony - the project to create an LGPL Qt clone http://harmony.ruhr.de

2 1

re:libgtk-use
by Mike Neuhaus 13 Oct '98

13 Oct '98

The problem is - gtk has no list of "extern" - definitions in one(!) file in the header - directory... and the link-process of libgtk needs many compiler-commandline-switches (...or use of gtkconfig). In libtk8.0 is this no problem. One (!) extern-list and simple link-process. Bud gtk has more from the good look and feel of free dynamic software. -- http://ekim.home.pages.de Mike Neuhaus ********PRO Heimerziehung heißt PRO Zukunft********** Die Heimerziehung bedarf nicht ihrer eigenen Abschaffung,sondern einer durch Innovation geprägten Reform

2 1

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 October 1998