On Apr 16, 2005, at 10:51 AM, Fred Kiefer wrote:
Well, it must be that gnustep-base did not build correctly. But I don't know why - perhaps the def file was not generated correctly, or perhaps, as is typical on Windows, some other library is interfering with the linking in some mystical way. Is there anyone else who uses Cygwin that has gnustep-base working?
I think that this is caused by the same problem that I reported about two weeks ago. The export file for the library is no longer created correctly, as there is a new subproject in base and the merged .def files contains duplicate entries now.
You did send me a patch for this, which didn't work. What we need here is a different way to create the .def file. Or have to wait until the new way of compilation for MinGW also works with cygwin. Perhaps updating the cygwin gcc to 3.4 would already do the trick.
No - sorry that the followups did not go to the list. It turns out I am not compiling gnustep-objc on Cygwin with the Startup script. When Bernd did this manually (following the README.Cygwin file), it worked.
The problem with the multiple subprojects is only in the CVS version of base, not the recent release versions.
_______________________________________________ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
