discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Q] GNUstep Building on Windows Platform(Latest CVS version)


From: Sungjin Chun
Subject: Re: [Q] GNUstep Building on Windows Platform(Latest CVS version)
Date: Fri, 17 Jun 2005 10:23:08 +0900

I'm not sure I have exact memory on this. But as far as I can remember, I have to build objc.dll with old style dll creation procedure; create .def and make .dll and create stub library for it. This solves my problem. If you need more information, contact me anytime. I also will find my old windows data.

Hope this can help you.

On Jun 17, 2005, at 3:48 AM, Fred Kiefer wrote:

Sungjin Chun wrote:

It seems that most current CVS version is changed in creating dll. I've
tried it with MinGW-3.2.0-rc-3.exe but failed. The error messages are
like following:

Info: resolving ___objc_class_name_Protocol by linking to
__imp____objc_class_name_Protocol (auto-import)
Info: resolving ___objc_class_name_Object by linking to
__imp____objc_class_name_Object (auto-import)
Cannot export .idata$4: symbol not found
Cannot export .idata$5: symbol not found
Cannot export .idata$6: symbol not found
Cannot export .text: symbol not found
Cannot export iconv_NULL_THUNK_DATA: symbol not found
Cannot export zlib1_NULL_THUNK_DATA: symbol not found
Creating library file: ./shared_obj/libgnustep-base.dll.a
collect2: ld returned 1 exit status
make[1]: *** [shared_obj/libgnustep-base.dll.a] Error 1
make: *** [libgnustep-base.all.library.variables] Error 2

I think my MinGW tool chains are not proper for building GNUstep on
Windows and I want to know if there's anyone who make success, pleast
let me know your tool selection; like version of MinGW, gcc and etc. My
version of gcc is 3.4.2



Did you ever find a soultion to this problem? I am stuck for weeks now
with exactly the same on MinGW. The strange thing is that compiling the
GNUstep base that comes with the installer works fine, while compiling
the CVS version gives this error message.
One thing that I have noted is that when linking all the libraries are
listed twice. I am not sure, if this is actually causing the problem or
if this is to do with the new subdirectories (these let the Cygwin
compilation fail).

Fred






reply via email to

[Prev in Thread] Current Thread [Next in Thread]