On 21 Sep 2002 at 4:48, Frank Heckenbach wrote:
[...]
I have found the problem. The source for the "Mingw special" edition (gcc-2.95.3-6) contains this in config/i386/xm-mingw32.h:
#ifdef TARGET_W9x /* This kludge must go, once we can get '/' to #work on W9x */ #define DIR_SEPARATOR_2 '/' #define DIR_SEPARATOR '\' #else #define DIR_SEPARATOR '/' #define DIR_SEPARATOR_2 '\' #endif
So, someone has opted not to support Win9x automatically. Murphy's Law has been proven once again - this is where I should have looked first, but it is where I looked last :(
And I suppose TARGET_W9x was not set when building it.
No. I didn't even realise that it existed :(
Well, I see. I had supposed something like this, but couldn't find it (obviously, since I don't have the "special edition").
In any case, for those who are interested, I have put a patched version of the gpc driver on the GPC ftp site: http://www.gnu-pascal.de/contrib/chief/win32/gpc_fix1.zip
This file contains only the exectuable, so I don't know what you changed in the source. Did you just set TARGET_W9x (but then the problem remains for those that build it without doing so), or change anything in gpc.c?
Nothing was changed in any file. I just rebuilt gpc.c with "-DTARGET_W9x" as part of the CFLAGS.
I could easily make gpc.c put a `' if either of the DIR_SEPARATOR's is `'. This will then also include Cygwin where it's not necessary AFAIK, but shouldn't hurt either, I guess.
I don't think that this is necessary. The whole problem was just another Windows "gotcha". I have added "-DTARGET_W9x" to the CFLAGS in the script that I use to build GPC for Mingw so that should cover the future. I still intend to keep looking at the config/i386/ files in any new Mingw gcc updates anyway, just to make sure that I am not missing anything ...
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~African_Chief email: African_Chief@bigfoot.com