Notice how that is NOT GCC's libobjc.
See my patch to that code.
I don't really care what libobjc GCC has because I have to use gnustep's.

Feel free to fix any of the steps that got us to this point, but don't
tell me that I am not using the right software when I followed the
published instructions.

Stay calm ...

Andrew is familiar with gcc, but not windows, you are familiar with
building GNUstep on windows, and neither of you know each others
background ... you just have two different viewpoints and I'm sure there
is no intention on either part to be awkward.

As far as I know (and I could be wrong on this) ... the libobjc provided
in the GNUstep CVS is a version which has been hacked to build nicely on
windows export the symbols windows needs in the way it needs them etc (I
don't know the details), but the mainline libobjc in the gcc project lacks
these modifications. On the other hand, the gcc version has various
bugfixes which are not in the version on gnustep cvs.

If this is not the case ... and the main gcc version of the library is
fine on windows, then the instructions we have for running gnustep on
windows are out of date ... and it would be good to know that so we can
change them.

If it is the case, the pair of you could do everyone a favour by finding
out what needs to be done to the main gcc version of the library to make
it usable with gnustep under windows, and get the changes into the main
version ... so we can remove the library from gnustep cvs.