Gpc

gpc@gnu.de

5400 discussions

beta didn't finish compiling
by Russ Whitaker 25 Sep '98

25 Sep '98

running slakware 3.5 on an i486. Liked gpc 2.0 so downloaded gpc-199808* put gpc-2.8.1 in /usr/local/src and unpacked gpc. Moved p to gpc-2.8.1 ran patch -s -p1 < p/diffs/gcc-2.8.1.diff while in /usr/local/src/gpc-2.8.1 ran ../gcc-2.8.1/configure --prefix=/usr ( also tried --prefix=/usr/local with same end result ) ran make LANGUAGES=pascal after about 45 min program quit with following lines: module.o: In function 'execute': /usr/local/src/gcc-2.8.1/p/module.c: 510 undefined reference to 'version_flag' module.o: In function 'module_must_be_recompiled': /usr/local/src/gcc-2.8.1/p/module.c: 796 undefined reference to 'version_flag' module.o: In function 'compile_module': /usr/local/src/gcc-2.8.1/p/module.c: 920 undefined reference to 'version_flag' Collect2 ld returned 1 exit status make[1]: ***[../gpc1] Error 1 etc fix, please thank you, Russ email russwhit(a)mind.net

1 0

beta didn't finish compiling
by Russ Whitaker 24 Sep '98

24 Sep '98

running slakware 3.5 on an i486. liked gpc 2.0 so downloaded gpc-199808 * put gcc-2.8.1 in /usr/local/src from dist. disk unpacked gpc-199808* and moved p to gcc-2.8.1 ran patch -s -p1 < p/diffs/gcc-2.8.1.diff ( while in gcc-2.8.1 directory) ran ../gcc-2.8.1/configure --prefix=/usr ( got same end result using --prefix=/usr/local ) ran make LANGUAGES=pascal about 45 min later program stopped with these last lines: module.o: In function 'execute': /usr/local/src/gcc-2.8.1/p/module.c: 510 undefined reference to 'version_flag' module o: In function 'compile_module': /usr/local/src/gcc-2.8.1/p/module.c: 796 undefined reference to 'version_flag' module.o: In function 'compile_module': /usr/local/src/gcc-2.8.1/p/module.c 920 undefined reference to 'version_flag' Collect2: ld returned 1 exit status make[1]: ***[../gpc1] Error 1 etc fix, please thanks, Russ email: russwhit(a)mind.net

1 0

Code Generation Problem, btw...
by Orlando Llanes 21 Sep '98

21 Sep '98

Now that I think about it, the problem I'm having might be a linking problem rather than a code generation problem (or maybe it's a combination of both?) See ya! Orlando Llanes "Meine Damen und Herren, Elvis hat soeben das Gebaeude verlassen!" "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 0

Re: Code generator problem?...
by Frank Heckenbach 18 Sep '98

18 Sep '98

Orlando Llanes wrote: > I recompiled a program to test my libs, and my program crashed. I > suspect that it's the importing of externals because I recompiled Bernie's > BWGraph libs and they also crashed (both his sources and my sources did > not crash with the previous version of GPC). The reason I suspect > importing of externals is because I printed a value that should have been > filled by an externally declared program, it seems as if none of the > routines declared outside are working properly. I'll have to warn you if > you need the code, I don't know if there's anyway to reduce it to > reproduce the error. BTW, I'm using the DOS version of GPC. Alright, as you may suppose, we can't find the problem with this description alone. So perhaps you can mail the sources to me privately, not to the list if they're big (please with an exact description how to compile them and how to run the program to reproduce the error)... -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Code generator problem?...
by Orlando Llanes 18 Sep '98

18 Sep '98

I recompiled a program to test my libs, and my program crashed. I suspect that it's the importing of externals because I recompiled Bernie's BWGraph libs and they also crashed (both his sources and my sources did not crash with the previous version of GPC). The reason I suspect importing of externals is because I printed a value that should have been filled by an externally declared program, it seems as if none of the routines declared outside are working properly. I'll have to warn you if you need the code, I don't know if there's anyway to reduce it to reproduce the error. BTW, I'm using the DOS version of GPC. See ya! Orlando Llanes "Meine Damen und Herren, Elvis hat soeben das Gebaeude verlassen!" "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 0

Re: gpc-19980830 with gcc-2.8.1 - version_flag is undefined
by Frank Heckenbach 15 Sep '98

15 Sep '98

Benedict Lofstedt wrote: Hi, > [please respond by direct mail as well as I'm only just in the process of > joining the list] I'm sending a Cc. > I cannot build gpc-19980830 with gcc-2.8.1. It seems that the patch in > p/diffs/gcc-2.8.1.diff is incomplete in regard to the 'toplev.c' file. It > only changes some empty lines, where it seems that it should make the > variable 'version_flag' available as en external symbol, as this is what > the file 'gbe.h' assumes to be the case: > > [...] > > Anyone with a patch ready for this? Yes, indeed the gcc-2.8.1.diff supplied with the last source release was incomplete. A corrected file has been uploaded to ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/gcc-2.8.1.diff.gz -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

gpc-19980830 with gcc-2.8.1 - version_flag is undefined
by Benedict Lofstedt 14 Sep '98

14 Sep '98

Hi, [please respond by direct mail as well as I'm only just in the process of joining the list] I cannot build gpc-19980830 with gcc-2.8.1. It seems that the patch in p/diffs/gcc-2.8.1.diff is incomplete in regard to the 'toplev.c' file. It only changes some empty lines, where it seems that it should make the variable 'version_flag' available as en external symbol, as this is what the file 'gbe.h' assumes to be the case: /* toplev.c */ extern char *progname; extern int version_flag; extern void pedwarn PVPROTO ((char *, ...)); extern void warning PVPROTO ((char *, ...)); extern void error PVPROTO ((char *, ...)); extern void fatal PVPROTO ((char *, ...)); extern void error_with_decl PVPROTO((tree, char *, ...)); extern void rest_of_decl_compilation PROTO ((tree, char *, int, int)); extern void warning_with_file_and_line PVPROTO ((char *, int, char *, ...)); The result is a linking problem. gcc -DIN_GCC -DGPC -DSVR4 -g -o ../gpc1 \ `cat stamp-gbe` ../c-aux-info.o ../c-iterate.o ../c-pragma.o ../choose-temp.o ../pexecute.o mkstemp.o gpc-common.o gpc-convert.o gpc-decl.o gpc-lang.o gpc-lex.o gpc-typeck.o module.o gpi-hash.o circle-buf.o objects.o parse.o rts.o types.o util.o setop.o version.o `if [ xobstack.o != x ]; then echo ../obstack.o; else true; fi` `case "gcc" in "cc") if [ xalloca.o != x ]; then echo ../alloca.o; else true; fi ;; esac` `if [ x != x ]; then echo ../; else true; fi` Undefined first referenced symbol in file version_flag module.o ld: fatal: Symbol referencing errors. No output written to ../gpc1 gmake[1]: *** [../gpc1] Error 1 Anyone with a patch ready for this? --- benedict -- Benedict Lofstedt <blofstedt(a)daimi.aau.dk> University of Aarhus, Department of Computer Science Fax: + 45 8942 3255 Building 540, Ny Munkegade, DK-8000 Aarhus C, Denmark. Phone: + 45 8942 3222

1 0

Re: gpc-19980830 binary for DJGPP
by Frank Heckenbach 09 Sep '98

09 Sep '98

Maurice Lombardi wrote: > I have found an other small error in this distribution. > The info files have short filenames gpc.iXX (which is good to enable to > work on plain DOS with 8.3 limitations), but in the gpc.inf file, in the > "Indirect:" section they are referred to with long filenames > gpc.info-XX, so that the info reader is unable to find them. This seems > the only error, and correcting manually these lines in the file gpc.inf > makes all to work properly. Thanks for the report. I've fixed it so it won't happen again with binaries I produce. Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

time bug
by Maurice Lombardi 08 Sep '98

08 Sep '98

Hi all I have finally found the answer to a very old DOS bug 34396148.5C71(a)ujf-grenoble.fr namely a bug appearing when running time.exe from command.com, and not when running it within rhide or under the bash shell. This has nothing to do with gpc, but it is due to a bizarre characteristic of DOS. When there is no explicit directory in a command, the name is looked for in the set of "internal commands", the current directory and in the paths listed is the PATH variable, in that order. And time is an "internal command" in DOS. So when you type "time.exe" DOS understands the command "time" with a parameter (which should be the new time) .exe (or exe with . as a separator), which makes no sense, and it barks invalid time. The workaround is to type explicitly the directory .\time.exe, so that there is no search for implicit directories. This is a common practice in unix shells, because the current directory is not prepended to the path list, but is usually never done in DOS. So remove the bug from the bug list and forget it. Or may be change the name time.p in the test list to tim.p (an change accordingly the makefile) to avoid the bug popping anew for an other user. Greetings Maurice -- Maurice Lombardi Laboratoire de Spectrometrie Physique, Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 51 45 44 mailto:Maurice.Lombardi@ujf-grenoble.fr

3 2

Re: time bug
by Frank Heckenbach 08 Sep '98

08 Sep '98

Maurice Lombardi wrote: > I have finally found the answer to a very old DOS bug > 34396148.5C71(a)ujf-grenoble.fr Glad to hear so. This was one of the few bugs in the list that I didn't really know what they were about... :-) > [...] > So remove the bug from the bug list and forget it. Or may be change the > name time.p in the test list to tim.p (an change accordingly the > makefile) to avoid the bug popping anew for an other user. Another solution would be to let the Makefile prepend ".\" to all file names under Dos, just as it prepends "./" on Unix. However, this test was part of the old test suite which isn't included in GPC anymore. I don't know if anyone still maintains that test suite. If so, s/he may change this... Anyway, I removed this bug from the list now, and for the first time (I think) since I have the list, DJGPP is not the system with the most system-specific bugs known... ;-) Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

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