Gpc January 1999

gpc@gnu.de

20 participants
34 discussions

Some help building GPC-19980830
by Ken Linder 09 Jan '99

09 Jan '99

Ok, Oh GPC & make masters... I was a good little boy & spent the best part of a day downloading GCC-2.8.1 and GPC-19980830. This is what I did & the error I got... Background Info: RH Linux 4.2 with GCC 2.7.2.1 1) gunzip GCC & GPC 2) untar GCC into /usr/src/gcc-2.8.1 3) untar gpc into /tmp/gpc 4) in the gcc source dir make a link ln -s p /tmp/gpc/p 5) apply the patch patch -p -s1 < p/gcc-2.8.1.diff 6) do in the gcc source dir configure -prefix=/usr 7) compile the thing in gcc source dir make LANGUAGES=pascal OK... problem... This is what I get... make[1]: entering directory '/tmp/gpc/p' make[1]: *** No rule to make target '../configure', needed by 'Makefile', stop. make[1]: leaving directory '/tmp/gpc/p' make: ***[gpc1] Error 2 Ok, oh mighty GPC wizards... What did I do wrong? Did I miss something? TNX... Ken Linder kc7rad(a)vegasnet.net

2 2

Re: Some help building GPC-19980830
by Frank Heckenbach 09 Jan '99

09 Jan '99

Ken Linder wrote: > Ok, Oh GPC & make masters... > > I was a good little boy & spent the best part of a day downloading > GCC-2.8.1 and GPC-19980830. This is what I did & the error I got... > > Background Info: RH Linux 4.2 with GCC 2.7.2.1 > > 1) gunzip GCC & GPC > 2) untar GCC into /usr/src/gcc-2.8.1 > 3) untar gpc into /tmp/gpc > 4) in the gcc source dir make a link ln -s p /tmp/gpc/p > > [...] > > make[1]: entering directory '/tmp/gpc/p' > make[1]: *** No rule to make target '../configure', needed by 'Makefile', > stop. I'm not sure, but ISTR that building GPC doesn't work with a symlink, because then `..' points to the wrong directory, and the GPC Makefiles use `..' a lot. So you might want to try moving the GPC directory below the GCC directory. Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Re: enum definition bug
by Frank Heckenbach 09 Jan '99

09 Jan '99

Miguel Lobo wrote: > By the way, it would be nice if an updated "known > bugs" list was put in GPC's web page. That way, when > a program doesn't do what I expected, I would > know if it's GPC's fault or mine. It is already there. Please look at: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html Hmmm... perhaps we should post a short FAQ here regularly that mentions the most important URLs and other stuff. Your bug was indeed already known and listed there (`enum types do not properly survive transport through two interfaces (russell2.pas, baby2.pas)'), but unfortunately not fixed yet. > And finally, if there is a beta release, would you > please build some binaries? (Compiling GCC is too much > for my computer and me; last time I tried I ran out > of disk space after about two hours of compilation). Which platform please? > Well, that was all by now. Happy new year, and good luck > fixing the bug :) Thanks. Happy New Year, Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

3 2

enum definition bug
by Miguel Lobo 03 Jan '99

03 Jan '99

This bug appears when you use an enumerated type, defined in a unit, in the "interface" of another unit which is used by the first (complicated, eh? :) ). Well, better look at the attached example to see what I mean. I compiled the main program with "--automake" and got "incompatible type" errors. By the way, it would be nice if an updated "known bugs" list was put in GPC's web page. That way, when a program doesn't do what I expected, I would know if it's GPC's fault or mine. And finally, if there is a beta release, would you please build some binaries? (Compiling GCC is too much for my computer and me; last time I tried I ran out of disk space after about two hours of compilation). Well, that was all by now. Happy new year, and good luck fixing the bug :) Miguel. uses bugenum1,bugenum2; begin q(e1); end. unit bugenum1; interface type enum = (e1,e2,e3,e4); function q(v: enum): boolean; implementation uses bugenum2; function q(v: enum): boolean; begin q :=p(v,e1); end; end. unit bugenum2; interface uses bugenum1; function p(v1,v2: enum): boolean; implementation function p(v1,v2: enum): boolean; begin p :=(v1=v2); end; end.

1 0

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 January 1999