On 25 Oct 2000, at 9:59, Frank Heckenbach wrote:
Prof. A Olowofoyeku (The African Chief) wrote:
On 24 Oct 2000, at 17:49, Michael Höhle wrote:
$ gpc helloworld.pas Assembler messages: for reading.open : No such file or directory
Hmm, what seems to be the problem here - and even more important - how to fix it?
I came across this problem a long time ago. Unfortunately I have no recollection of how I fixed it (it may have something to do with 'sh' or it may not - I know that this is not very helpful). Frank/Peter may have records of our discussions on that problem and how I reported that it was fixed - if they don't then sorry ...
Yes, I think you reported that it was solved by replacing sh.exe with bash.exe.
But I don't know what exactly is the cause of the problem. I'm also wondering why a shell seems to be involved in the step between the compiler and assembler at all (I don't think it's so on other systems) -- perhaps this is a reason why compilation is so slow on Windoze (as The Chief reported). -- But I'm only speculating as I don't use this system, but if anyone who does feels like investigating these issues further, it might help...
I think I remember now, that using 'sh.exe' (or at least some particular versions thereof) messes up some things internally during the process of building GPC, and so causes a broken GPC to be built. Thus, after you copy 'bash.exe' over 'sh.exe', you will need to rebuild GPC from the scratch (i.e., everything afresh). However, some recent versions of the Cygwin 'sh.exe' (in ash-2000xxx.tar.gz) seem to have fixed this problem. You need to go to the Cygwin site and download the latest version of 'ash'. This may solve the problem. If it doesn't, then you will need to copy bash.exe over sh.exe (in either case you will still need to rebuild GPC from the scratch).
Best regards, The Chief --------- Prof. Abimbola Olowofoyeku (The African Chief) Email: African_Chief@bigfoot.com Author of Chief's Installer Pro v5.23 for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm