According to Jan-Jaap van der Heijden:
To Peter: since this GPC is searching for this obsolete 'djgpp.lnk', I assume you are indeed using v2.0. In that case you'd better upgrade to 2.01 to stop this confusion.
I was sure that I am using v2.01, but I re-installed my `djdev201.zip' and `gcc2721b.zip', thus the new Alpha gpc-970510 should definitly (?) be v2.01.
Greetings,
Peter
Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski@uni-essen.de - http://home.pages.de/~peter.gerwinski/ [970201] maintainer GNU Pascal [970510] - http://home.pages.de/~gnu-pascal/ [970125]
On Sun, 11 May 1997, Peter Gerwinski wrote:
According to Jan-Jaap van der Heijden:
To Peter: since this GPC is searching for this obsolete 'djgpp.lnk', I assume you are indeed using v2.0. In that case you'd better upgrade to 2.01 to stop this confusion.
I was sure that I am using v2.01, but I re-installed my `djdev201.zip' and `gcc2721b.zip', thus the new Alpha gpc-970510 should definitly (?) be v2.01.
Well, gpc alpha 05/10 still says "ld: can't find djgpp.lnk" BUT, "gpc -v" says "2.0(2.7.2.1)" and not an alpha version number. Did I install it right? I think so. gpc2.0 (non alpha) used to work fine.
"gcc -v" reports 2.7.2.1 and works. (compiles hello.c ;) /djgpp/manifest has djdev201.mft, so I think I have djgpp v2.01. I only started using djgpp after 2.01 came out. Is there any other way to find out? (yes, seems like a newbie question ;)
I checked my path, and djgpp's ld.exe seems to be the one that gets executed (I also have fpk-pascal, which has an older version). Is there any way I can check version numbers (compared to what?) of these?
Can I do something like "gpc --"keep all temporary files" and examine those? What would I be looking for??
I tried both command line, and rhide.
I (currently) don't have the disk space to install the source tree, and the files created while compiling. <sniff> so I can't check that.
On a side note: gpc.inf doesn't work (no top node) But gpc.inf and gpc.i1 both reference and contain a top node. I can't see why "info --file gpc.inf" complains...
gcc.inf/gcc.i1 look the same (at least in structure) and work.
Greetings,
PeterDipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski@uni-essen.de - http://home.pages.de/~peter.gerwinski/ [970201] maintainer GNU Pascal [970510] - http://home.pages.de/~gnu-pascal/ [970125]
Cheers Berend De Schouwer.
On Wed, 14 May 1997, Berend De Schouwer wrote:
On Sun, 11 May 1997, Peter Gerwinski wrote:
According to Jan-Jaap van der Heijden:
To Peter: since this GPC is searching for this obsolete 'djgpp.lnk', I assume you are indeed using v2.0. In that case you'd better upgrade to 2.01 to stop this confusion.
I was sure that I am using v2.01, but I re-installed my `djdev201.zip' and `gcc2721b.zip', thus the new Alpha gpc-970510 should definitly (?) be v2.01.
Well, gpc alpha 05/10 still says "ld: can't find djgpp.lnk"
I found the error: it's in LIB/SPECS.GPC This file has somehow survived from djgpp-2.0 days and thus references "djgpp.lnk" instead of "djgpp.djl", whether you use djgpp v2.01 or not.
The link_command should look like:
*link_command: %{!c:%{!M:%{!MM:%{!E:%{!S:ld %l %X %{o*} %{A} %{d} %{e*} %{m} %{N} %{n} \ %{r} %{s} %{t} %{u*} %{x} %{z}\ %{!A:%{!nostartfiles:%{!nostdlib:%S}}} %{static:}\ %{L*} %D %{T*} %o -Tdjgpp.djl\ %{!nostdlib:-lgcc -lgpc -lm %L -lgcc %{!A:%E}}}}}}} %{!c:%{!M:%{!MM:%{!E:%{!S:stubify %{v} %{o*:%*} %{!o*:a.out}}}}}}
You're in trouble if you see:
*link_command: %{!c:%{!M:%{!MM:%{!E:%{!S:ld %l %X %{o*} %{A} %{d} %{e*} %{m} %{N} %{n} \ %{r} %{s} %{t} %{u*} %{x} %{z}\ %{!A:%{!nostartfiles:%{!nostdlib:%S}}} %{static:}\ %{L*} %D %{T*} %o -Tdjgpp.lnk\ %{!nostdlib:-lgcc -lgpc -lm %L -lgcc %{!A:%E}}}}}}} %{!c:%{!M:%{!MM:%{!E:%{!S:stubify %{v} %{o*:%*} %{!o*:a.out}}}}}}
To solve this, you can either use the "specs.gpc" from gpc-2.0 (which worked a.f.a.i.k.) or save and uudecode this:
begin 644 specs.gpc M*F%S;3H-"@T*#0HJ87-M7V9I;F%L.@T*#0H-"BIC<'`Z#0HE>W!O<VEX.BU$ M7U!/4TE87U-/55)#17T-"@T**F-C,3H-"@T*#0HJ8V,Q<&QU<SH-"@T*#0HJ M96YD9FEL93H-"@T*#0HJ;&EN:SH-"@T*#0HJ;&EN:U]C;VUM86YD.@T*)7LA M8SHE>R%-.B5[(4U-.B5[(44Z)7LA4SIL9"`E;"`E6"`E>V\J?2`E>T%]("5[ M9'T@)7ME*GT@)7MM?2`E>TY]("5[;GT@7`T*"25[<GT@)7MS?2`E>W1]("5[ M=2I]("5[>'T@)7MZ?5P-"@DE>R%!.B5[(6YO<W1A<G1F:6QE<SHE>R%N;W-T M9&QI8CHE4WU]?2`E>W-T871I8SI]7`T*"25[3"I]("5$("5[5"I]("5O("U4 M9&IG<'`N9&IL7`T*"25[(6YO<W1D;&EB.BUL9V-C("UL9W!C("UL;2`E3"`M M;&=C8R`E>R%!.B5%?7U]?7U]?0T*)7LA8SHE>R%-.B5[(4U-.B5[(44Z)7LA M4SIS='5B:69Y("5[=GT@)7MO*CHE*GT@)7LA;RHZ82YO=71]?7U]?7T@#0H- M"BIL:6(Z#0HM;&,-"@T**G-T87)T9FEL93H-"B5[<&<Z9V-R=#`N;R5S?25[ M(7!G.B5[<#IM8W)T,"YO)7-])7LA<#IC<G0P+F\E<WU]#0H-"BIS=VET8VAE M<U]N965D7W-P86-E<SH-"@T*#0HJ<VEG;F5D7V-H87(Z#0HE>V9U;G-I9VYE M9"UC:&%R.BU$7U]#2$%27U5.4TE'3D5$7U]]#0H-"BIP<F5D969I;F5S.@T* M+41U;FEX("U$:3,X-B`M1$=/,S(@+41-4T1/4R`M1$1*1U!0/3(@+41$2D=0 C4%]-24Y/4CTQ#0H-"BIC<F]S<U]C;VUP:6QE.@T*,`T*#0H` ` end
On a side note: gpc.inf doesn't work (no top node) But gpc.inf and gpc.i1 both reference and contain a top node. I can't see why "info --file gpc.inf" complains...
gcc.inf/gcc.i1 look the same (at least in structure) and work.
I'm not an expert in info files, but isn't the top-node the entry for a program in the "dir" file?
In that case, try adding GPC, locate the GCC entry:
* GCC: (gcc.inf). The GNU C, C++, and Objective-C Compiler
And add GPC somewhere, like this:
* GPC: (gpc.inf). The GNU Pascal Compiler
Hope this helps,
JanJaap
--- With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC1925.
BDS>gpc.inf doesn't work (no top node) BDS>But gpc.inf and gpc.i1 both reference and contain a top node. I BDS>can't see why "info --file gpc.inf" complains... BDS> BDS>gcc.inf/gcc.i1 look the same (at least in structure) and work. it's some problem with structure - i bet the makeinfo version (top of dokument - this file is produced by ... or smth. like that) differs. if that's the case - try to get an newer version of the info programm...
that's been the solution to the problem on my system. BDS>Cheers BDS>Berend De Schouwer.
Chris
--- HomeBox : Chateau - +49(0)8677 911940(V.34) 911941(ISDN) *! New Address - C.Wendt@chateau.line.org !*
## CrossPoint v3.11 ##
-
Berend De Schouwer -
C.WENDT＠CHATEAU.line.org -
Jan-Jaap van der Heijden -
Peter Gerwinski