Hi
I believe this was mentioned before...
I installed alpha 4/20 (without making a backup, tch..) on djgpp v2 I can compile and get .o files, but the linking stage doesn't find djgpp.lnk (I assume gpc does "ld @djgpp.lnk") at some stage.
I don't mind typing this myself, but I haven't got a sample .lnk file to work with (silly me ;).
Any help will be appreciated.
Cheers Berend De Schouwer
P.S. gcc works fine.
On Fri, 9 May 1997, Berend De Schouwer wrote:
Hi
I believe this was mentioned before...
I installed alpha 4/20 (without making a backup, tch..) on djgpp v2 I can compile and get .o files, but the linking stage doesn't find djgpp.lnk (I assume gpc does "ld @djgpp.lnk") at some stage.
I don't mind typing this myself, but I haven't got a sample .lnk file to work with (silly me ;).
I too think we have seen this error before. Maybe it's FAQ-able.
djgpp v2.0 uses the linker script 'djgpp.lnk' (in the djgpp 'lib' dir). djgpp v2.01 uses 'djgpp.djl' for this purpose.
So, either Peter (who built this GPC binary) is using djgpp v2.0 and you have v2.01, or vice versa.
I haven't seen this error with djgpp v2.01, but I always build my own compiler binaries.
BTW: 'djgpp.djl' and 'djgpp.lnk' are different files so renaming isn't going to work.
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.
Hope this helps, JanJaap
CC: Peter Gerwinski --- 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.