[Mono-list] Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released

[Daniel Morgan]

I could not get mono to build with csc from ms .net; however, I was able 
to build mono using mcs installed via the installer.

Also what helped, I did not have ms .net anywhere in my PATH.

Wade Berrier wrote:

>>- also, as Kornel said, the runtime should not be statically linked,
>>but instead it should be
>>  dynamically linked against a mono-1.dll file. This should be the
>>default in our build process, so I don't know why this isn't
>>happening. What configure arguments are you
>>using when building the runtime ?
>>
>>    
>>
>
>First, from Kornél:
>
>"Note that most of your modifications are welcome and I like them
>(especially
>that you moved native exe's to bin directory)"
>
>I didn't do anything special here.  That's the way the build came out.
>The only ./configure switch I used was "--prefix="
>
>Here's the scoop on the static linking.
>
>I ended up compiling gtk-sharp 1 and 2 with Paco's snapshot of cygwin
>March of 2004.  (gcc 3.3.1 cygming special).  That was the only way I
>get get it to link.
>
>Then I noticed that when I built mono on the newest cygwin, the native
>exe's (mono.exe, monodis.exe, etc...) were statically linked and each
>around 9 MB.
>
>So, I then tried to compile mono under Paco's environment and ended up
>getting errors: /monobuild/mono/mono/handles/semdel: No
>such file or directory
>
>So I packaged up the statically linked version.
>
>I'd like to be able to build with the latest cygwin but have not been
>able to get it linking correctly:
>
>*** Warning: linker path does not have real file for library -lintl.
>*** I have the capability to make that library automatically link in
>when
>*** you link to this library. But I can only do this if you have a
>*** shared version of the library, which you do not appear to have
>*** because I did check the linker path looking for a file starting
>*** with libintl and none of the candidates passed a file format test
>*** using a file magic. Last file
>checked: /cygdrive/c/mono/Mono-1.1.8.3/bin/libintl-1.dll
>*** Warning: libtool could not satisfy all declared inter-library
>*** dependencies of module libglibsharpglue. Therefore, libtool will
>create
>*** a static module, that should work as long as the dlopening
>*** application is linked with the -dlopen flag.
>ar cru .libs/libglibsharpglue.a error.o list.o object.o slist.o type.o
>unichar.o value.o valuearray.o
>ranlib .libs/libglibsharpglue.a
>creating libglibsharpglue.la
>
>I'm not sure why the file magic is failing with the latest cygwin.  I
>would at least like to build with the same version of cygwin that our
>buildbot is using so that I don't run into all these last minute build
>issues.
>
>I was also thinking: maybe we should be using msys/mingw instead of
>cygwin.  They provide a less-changing environment.  Some excerpts from
>their website:
>
>.. (previously MinGW was a moving target with all the constant updates
>to individual packages, but now it is easier to verify things as being
>"MinGW 1.0 compatible").  ... The updates to this package and it's
>utilities are more controlled ...
>
>We're using the mingw compiler from cygwin anyway.
>
>That's the scoop.  As soon as these issues are solved I'll be able to
>post a windows build of mono that includes the dll files.
>
>Wade
>
>_______________________________________________
>Mono-list maillist  -  Mono-list at lists.ximian.com
>http://lists.ximian.com/mailman/listinfo/mono-list
>
>  
>