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

Wed Oct 5 07:49:40 EDT 2005

Hi,

Previously I compiled trunk from SVN.

This time I downloaded
http://go-mono.com/sources/mono-1.1/mono-1.1.9.1.tar.gz

And compiled in the same environment and got the same result you described.
(useless mono.exe and no MonoPosixHelper.dll) But exe's linked to mono-1.dll
unlike in the installer.

Then I applied the patch from Zoltán you mentioned to configure and compiled
in the same environment with success without any other modifications.

Note that libtool contained -mno-cygwin in my environment as well before the
patch so this patch is really required.

Executed:
configure, make, make install.

Everything compiled, mono-1.dll and MonoPosixHelper.dll were created and
exe's link to mono-1.dll. Binaries are not dependent on cygwin. This time I
got the result I expected. Congratulations to Zoltán for finding the
problem.

This is how the next Windows Setup of Mono should look like.

> I like using the zip files for build time deps and they are easy to
> include with the installer.

You are right.:)

Could you please update
http://www.mono-project.com/Using_Mono_on_Windows#Building_Mono_on_Windows
with your experiences (and possibly with my experiences as well that I
described or with anything else you know that can be difficicult without
some help) of building Mono and link
http://www.gimp.org/~tml/gimp/win32/downloads.html as the source of
dependencies to help others who want to build Mono on Windows.

When I set up my new cygwin build environment it was rally easy but I
remember that it was extremely difficult to set up a cygwin environment for
the first time that contained all requirements. Altough I had some
experience in Linux I never used cygwin before that made things more
difficult. The linked article may be good but it's outdated and currently
it's much easier to set up a build environment. For example currently there
are a lot of unsure things "possibly called gcc-mingw", "or activestate's
perl", "autotools". There should not be any "or" and "possibly" or
pseudo-package like "autotools". This only makes people confused. There
should be listed only the packages that has to be selected in addition to
default packages if you want to build
Mono.

File names of required ziped dependencies should be mentioned as well.

The only thig you have to do is to install cygwin with default packages and
some extra devel packages and install dependencies from zip files. But this
is not so obvious for someone who tries to do this for the first time that's
while a short but correct guide is required.

Also note that it is documented that it's recommended to use dependencies
from an existing Mono installation installed using the setup but it's not so
obvious. It should be documented how to configure the build environment to
use dependencies from that directory.

Usually people who use Mono on Windows have little or no experience at all
in Linux so they need some help. But the documentation should not be too
long as it won't be read by anybody.:)

Kornél

----- Original Message -----
From: "Wade Berrier" <wberrier at novell.com>
To: "Kornél Pál" <kornelpal at hotmail.com>
Cc: "Zoltan Varga" <vargaz at gmail.com>; <dick at ximian.com>; "Raja R Harinath"
<RHarinath at novell.com>; <mono-devel-list at lists.ximian.com>
Sent: Wednesday, October 05, 2005 2:51 AM
Subject: Re: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released]

> Hi Kornél,
>
> Thanks for the details!
>
> I guess the only question I have is whether the 1.1.9.1 tarball works
> for you in this environment.
>
> Zoltan checked in a libtool patch into trunk that fixes the issues I was
> having:
>
> http://lists.ximian.com/pipermail/mono-patches/2005-October/065089.html
>
> Sorry the gettext-dev wasn't on the list, it was left out for some
> reason.
>
> I like using the zip files for build time deps and they are easy to
> include with the installer.
>
> We're getting there...
>
> Thanks again!
>
> Wade
>
>
>
>
> On Wed, 2005-10-05 at 02:24 +0200, Kornél Pál wrote:
>> > Are you able to build?  If so, are you using the latest cygwin?  What
>> > deps are you using?
>>
>> I tried to reproduce you build environment:
>>
>> I installed a brand new basic cygwin (latest installer, latest packages)
>> only with default components and Mono requirements selected. (See later
>> the
>> exact list of packages.)
>>
>> Then I extracted the directories inside the zip's you listed to C:\cygwin
>> or
>> C:\cygwin\usr depending on where the target directory existed.
>> Overwritten
>> existing
>> files. Edited glib-2.0 .pc files to make prefix=/usr.
>>
>> Executed:
>>  autogen.sh, make, make install.
>>
>> Everything compiled, mono-1.dll and MonoPosixHelper.dll were created and
>> exe's link to mono-1.dll. Binaries are not dependent on cygwin. So I got
>> the
>> result I expected.
>>
>> Note that however that I had to download and install
>> gettext-dev-0.14.5.zip
>> as well that wasn't listed by you. If you used this package from cygwin
>> it
>> may cause problems but I did not try it.
>>
>> Also note that I prefer to use cygwin pkgconf as Win32 pkgconf replaces
>> prefix in .pc with ../../ relative to the .pc file that is something I
>> really don't like. So I did not use pkgconfig-0.15.zip at all. I used
>> cygwin
>> pkgconfig instead.
>>
>> As I can remember I selected the following components in Devel and the
>> others were added by the setup:
>>
>> autoconf
>> automake
>> binutils
>> bison
>> gcc
>> libtool
>> make
>>
>> Exact list of installed packages (from install log):
>> terminfo
>> texinfo
>> _update-info-dir
>> libreadline6
>> libncurses8
>> bash
>> base-passwd
>> libiconv2
>> libintl2
>> cygwin
>> libintl3
>> alternatives
>> ash
>> m4
>> libgdbm4
>> libdb4.2
>> libdb4.3
>> crypt
>> expat
>> bzip2
>> libbz2_1
>> perl
>> mktemp
>> autoconf2.1
>> autoconf2.5
>> autoconf
>> automake1.4
>> automake1.6
>> automake1.7
>> automake1.8
>> automake1.9
>> coreutils
>> findutils
>> sed
>> base-files
>> binutils
>> bison
>> libncurses7
>> ncurses
>> clear
>> cygrunsrv
>> libpopt0
>> cygutils
>> gawk
>> groff
>> gzip
>> termcap
>> libpcre0
>> less
>> libcharset1
>> libiconv
>> man
>> cygwin-doc
>> diffutils
>> editrights
>> zlib
>> file
>> w32api
>> mingw-runtime
>> gcc-mingw-core
>> gcc-core
>> gcc-mingw-g++
>> gcc-g++
>> gcc
>> libgdbm3
>> gdbm
>> glib
>> libintl1
>> libintl
>> grep
>> libapr0
>> libgdbm
>> libgdbm-devel
>> libltdl3
>> libncurses5
>> libncurses6
>> libreadline4
>> libreadline5
>> libtool1.5
>> openssl097
>> openssl
>> links
>> login
>> lynx
>> make
>> mc
>> minires
>> openssh
>> patch
>> patchutils
>> pkgconfig
>> tar
>> wget
>> which
>>
>> Note that this list includes some of my needs not required by Mono like
>> mc,
>> wget, openssh, patch, ...
>>
>> And of course this list don't include dependencies installed from zip
>> files.
>>
>> And note that libiconv was installed as something needed it, but was
>> overwritten with the version in the zip file.
>>
>> I like this new environment so I decided to use it instead of my previous
>> cygwin installation that has some older and some unnecessary packages.:)
>>
>> Hope this helps.
>>
>> Kornél
>>
>> ----- Original Message -----
>> From: "Wade Berrier" <wberrier at novell.com>
>> To: "Kornél Pál" <kornelpal at hotmail.com>
>> Cc: "Zoltan Varga" <vargaz at gmail.com>; <dick at ximian.com>; "Raja R
>> Harinath"
>> <RHarinath at novell.com>; <mono-devel-list at lists.ximian.com>
>> Sent: Tuesday, October 04, 2005 7:26 PM
>> Subject: Re: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer
>> Released]
>>
>>
>> > On Tue, 2005-10-04 at 18:36 +0200, Kornél Pál wrote:
>> >> > From: Wade Berrier
>> >> > So it probably turns out that System.XML is the first dll that gets
>> >> > compiled from the mini wrapper?
>> >>
>> >> Yes, it is, but this was mentioned by Zoltán in the message you
>> >> replyed
>> >> to:
>> >>
>> >> >> From: Zoltan Varga
>> >> >> The line which compiles System.XML is the first time the newly
>> >> >> compiled runtime is executed, ...
>> >
>> > True, must have missed that, thank you for pointing that out.
>> >
>> >
>> >>
>> >> Also note that I get some zombie mono.exe like this when I use a glib
>> >> that
>> >> is compiled to use cygwin (or use cygwing glib-devel package). So
>> >> check
>> >> this
>> >> as it may be the cause of the behaviour you experience.
>> >
>> > As noted in a previous email in this thread, I'm using the glib deps
>> > from listed on tml's win32 gtk download page:
>> >
>> > ftp://ftp.gtk.org/pub/gtk/v2.6/win32/glib-2.6.6.zip
>> > ftp://ftp.gtk.org/pub/gtk/v2.6/win32/glib-dev-2.6.6.zip
>> > http://www.gimp.org/~tml/gimp/win32/pkgconfig-0.15.zip
>> > http://www.gimp.org/~tml/gimp/win32/libiconv-1.9.1.bin.woe32.zip
>> > http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip
>> >
>> > Also, Zoltan is also having the same issues that I'm having with the
>> > latest cygwin, where as he was able to compile about a month ago.
>> >
>> > Are you able to build?  If so, are you using the latest cygwin?  What
>> > deps are you using?
>> >
>> > Wade
>> >
>> >
>> >
>> >>
>> >> Kornél
>> >>
>> >> ----- Original Message -----
>> >> From: "Wade Berrier" <wberrier at novell.com>
>> >> To: "Zoltan Varga" <vargaz at gmail.com>
>> >> Cc: <dick at ximian.com>; "Raja R Harinath" <RHarinath at novell.com>;
>> >> <mono-devel-list at lists.ximian.com>
>> >> Sent: Tuesday, October 04, 2005 6:09 PM
>> >> Subject: Re: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer
>> >> Released]
>> >>
>> >>
>> >> > On Tue, 2005-10-04 at 15:14 +0200, Zoltan Varga wrote:
>> >> >>                                                      Hi,
>> >> >>
>> >> >>   The problem is not with System.XML, but with the runtime itself.
>> >> >> The
>> >> >> line which compiles
>> >> >> System.XML is the first time the newly compiled runtime is
>> >> >> executed,
>> >> >> all prior commands
>> >> >> use the locally installed mcs and the locally installed runtime.
>> >> >> Try
>> >> >> running
>> >> >>
>> >> >> /tmp/scratch/mono-1.1.9.1/runtime/mono-wrapper
>> >> >>
>> >> >> without any parameters to see if the runtime works at all.
>> >> >>
>> >> >
>> >> > You're right on this one.  Running this doesn't do anything except
>> >> > return an error code of 255.
>> >> >
>> >> > So it probably turns out that System.XML is the first dll that gets
>> >> > compiled from the mini wrapper?
>> >> >
>> >> > I wonder what could be causing this?
>> >> >
>> >> > Wade
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >> On 10/4/05, Raja R Harinath <rharinath at novell.com> wrote:
>> >> >> > Hi,
>> >> >> >
>> >> >> > Wade Berrier <wberrier at novell.com> writes:
>> >> >> >
>> >> >> > [snip]
>> >> >> > > So, now when I build, the .dll files are generated, but now the
>> >> >> > > build
>> >> >> > > fails with the same error I got when building under Paco's
>> >> >> > > cygwin
>> >> >> > > environment of Mar 2004:
>> >> >> > >
>> >> >> > > MONO_PATH="../../class/lib/basic;
>> >> >> > > $MONO_PATH" /tmp/scratch/mono-1.1.9.1/runtime/mono-wrapper
>> >> >> > > ../../class/lib/basic/mcs.exe  /nologo
>> >> >> > > /optimize -d:NET_1_1 -d:ONLY_1_1 -d:BOOTSTRAP_WITH_OLDLIB
>> >> >> > > /debug+
>> >> >> > > /debug:full
>> >> >> > > /noconfig -r:mscorlib.dll -r:System.dll -nowarn:0162 -nowarn:0618
>> >> >> > > -nowarn:0612
>> >> >> > >  -target:library -out:System.Xml.dll `echo
>> >> >> > > System.Xml.XPath/Parser.cs
>> >> >> > > Mono.Xml.Xsl/PatternParser.cs Mono.Xml.Xsl/PatternTokenizer.cs
>> >> >> > > |
>> >> >> > > tr
>> >> >> > > '/' '\\\\'` @../../build/deps/basic_System.Xml.dll.response
>> >> >> > > make[8]: Leaving directory
>> >> >> > > `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML'
>> >> >> > > make[7]: Leaving directory
>> >> >> > > `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML'
>> >> >> > > make[6]: Leaving directory
>> >> >> > > `/tmp/scratch/mono-1.1.9.1/mcs/class'
>> >> >> > > make[5]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs'
>> >> >> > > make[8]: *** [../../class/lib/basic/System.Xml.dll] Error 255
>> >> >> >
>> >> >> > This is the actual error.  It probably means that the runtime
>> >> >> > couldn't
>> >> >> > execute (it uses mono-wrapper).
>> >> >> >
>> >> >> > > /tmp/scratch/mono-1.1.9.1/libtool: line
>> >> >> > > 6594: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: No such
>> >> >> > > file
>> >> >> > > or
>> >> >> > > directory
>> >> >> > > /tmp/scratch/mono-1.1.9.1/libtool: line 6594:
>> >> >> > > exec: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: cannot
>> >> >> > > execute:
>> >> >> > > No
>> >> >> > > such file or directory
>> >> >> >
>> >> >> > This is not actually an error, even though it looks like one.
>> >> >> >
>> >> >> > - Hari
>> >> >> >
>> >> >>
>> >> >
>> >> > _______________________________________________
>> >> > Mono-devel-list mailing list
>> >> > Mono-devel-list at lists.ximian.com
>> >> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
>> >> >
>> >>
>> >
>> > _______________________________________________
>> > Mono-devel-list mailing list
>> > Mono-devel-list at lists.ximian.com
>> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
>> >
>>
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>