<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <div class="moz-cite-prefix">On 13/05/2014 23:26, Martin Thwaites
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAH07y4TcFDZn7jLFg6ammTfw3MQVg3mc79cibtLp8EbmyMRqZA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>
                  <div>Hi Alex,<br>
                    <br>
                  </div>
                  I've been giving your tutorial ago, and I have some
                  things that may be good to add...<br>
                  <br>
                </div>
                firstly, I'm building from git, and I checked it out
                using the visual studio clone.  I think this lead to a
                line endings error, so you need to run the script in a
                way that uses them properly.  I found that if you run it
                with "bash -x -o igncr autogen.sh
                --prefix="c:\monoinstall" --with-preview=yes" it seems
                to do the trick.<br>
                <br>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Hi Martin, I spotted your comment on there :) I'm glad you found it
    useful and many thanks for the feedback. I will make sure to get
    that incorporated shortly. You also reminded me to add that the path
    root should not contain spaces or the build will fail, and I believe
    that building as a user with a space in the name may also cause
    problems.<br>
    <br>
    I have also taken Bryan's comment in an earlier thread on-board, on
    automating the Cygwin package pull-down. I will aim to put a noddy
    script together to do this when I get a chance.<br>
    <br>
    <blockquote
cite="mid:CAH07y4TcFDZn7jLFg6ammTfw3MQVg3mc79cibtLp8EbmyMRqZA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>I've now come across another error that you may be
                able to help with:<br>
                === configuring in eglib
                (/cygdrive/c/Users/Martin/Source/Repos/mono/eglib)<br>
                configure: WARNING: no configuration information is in
                eglib<br>
                === configuring in libgc
                (/cygdrive/c/Users/Martin/Source/Repos/mono/libgc)<br>
                configure: running /bin/sh ./configure
                --disable-option-checking '--prefix=/usr/local' 
                '--host=i686-pc-mingw32' 'host_alias=i686-pc-mingw32'
                'CPPFLAGS_FOR_EGLIB=' 'CFLAGS_FOR_EGLIB='
                '--disable-embed-check' '--with-libgc-threads=win32'
                '--enable-win32-dllmain=yes' '--enable-parallel-mark'
                'CPPFLAGS_FOR_LIBGC=-DWINVER=0x0500
                -D_WIN32_WINNT=0x0500 -D_WIN32_IE=0x0501 -D_UNICODE
                -DUNICODE -DWIN32_THREADS -DFD_SETSIZE=1024'
                'CFLAGS_FOR_LIBGC= -g -mno-tls-direct-seg-refs
                -DGC_BUILD -DGC_NOT_DLL' --cache-file=/dev/null
                --srcdir=.<br>
                /bin/sh: ./configure: No such file or directory<br>
                configure: error: ./configure failed for libgc<br>
                <br>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    I don't have a good answer for you here I am afraid. However the
    fact that you're seeing problems in eglib and libgc relating to
    configuration is interesting as I have had ongoing problems here too
    when trying to cross-compile for ARM targets. I mentioned some of
    this in an earlier thread - <a class="moz-txt-link-freetext" href="http://bit.ly/1gCDDXv">http://bit.ly/1gCDDXv</a><br>
    <br>
    To cut a long story short, when we're cross-compiling with
    Yocto/OpenEmbedded we may have three different sets of relevant Mono
    tools (at least). There's whatever the user has installed on their
    host system for their own use. Then there's a 'native' Mono which is
    built as a pre-cursor to building Mono to run on the configured
    target i.e. two step build as per <a class="moz-txt-link-freetext" href="http://bit.ly/1v3bqCs">http://bit.ly/1v3bqCs</a><br>
    <br>
    What I've been seeing is that the standard autotools templating
    results in incorrect dependencies on the host Mono installation
    rather that the native/target Mono.<br>
    <br>
    This can cause build failures depending on which particular version
    of Mono is actually installed on the host. <br>
    <br>
    I worked through this with a guy who was trying to build on Linux
    Mint with Mono installed, and which seemed to bring it out into the
    open for us.<br>
    <br>
    The solution was for me to modify the acinclude.m4 templates before
    I do the configuration to make sure they are specifying the correct
    prefixed libtool rather than defaulting to whatever is about on the
    build machine -<br>
    <br>
     ${S}/autogen.sh --verbose || bbnote "${PN} failed to autogen.sh"<br>
        sed -e "s|slash\}libtool|slash\}${HOST_SYS}-libtool|" -i
    acinclude.m4<br>
        sed -e "s|slash\}libtool|slash\}../${HOST_SYS}-libtool|" -i
    libgc/acinclude.m4<br>
        sed -e "s|slash\}libtool|slash\}../${HOST_SYS}-libtool|" -i
    eglib/acinclude.m4<br>
        sed -e "s|r/libtool|r/${HOST_SYS}-libtool|" -i
    runtime/mono-wrapper.in<br>
        sed -e "s|r/libtool|r/${HOST_SYS}-libtool|" -i
    runtime/monodis-wrapper.in<br>
    <br>
<a class="moz-txt-link-freetext" href="http://git.yoctoproject.org/cgit/cgit.cgi/meta-mono/tree/recipes-mono/mono/mono-3.4.0.inc">http://git.yoctoproject.org/cgit/cgit.cgi/meta-mono/tree/recipes-mono/mono/mono-3.4.0.inc</a><br>
    <br>
    This may or may not be related to what you are seeing...<br>
    <br>
    Best Regards,<br>
    <br>
    Alex<br>
    <br>
    <blockquote
cite="mid:CAH07y4TcFDZn7jLFg6ammTfw3MQVg3mc79cibtLp8EbmyMRqZA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>I'm now at a loss.<br>
              <br>
            </div>
            As I've stated before, what I'm looking to do is be able to
            develop mono (not develop with) in Visual Studio.  Maybe the
            stuff the Miguel is doing will help, but I just had a bit of
            time so thought I'd give your stuff ago.<br>
            <br>
          </div>
          Thanks,<br>
        </div>
        Martin<br>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On 5 May 2014 03:52, Alex J Lennon <span
            dir="ltr"><<a moz-do-not-send="true"
              href="mailto:ajlennon@dynamicdevices.co.uk"
              target="_blank">ajlennon@dynamicdevices.co.uk</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div class=""><br>
              On 05/05/2014 03:44, Konaju Games (Dev) wrote:<br>
              <br>
              > With Cygwin, there is one change to make to etc/fstab
              before starting<br>
              > a build.  You need to add noacl to the cygdrive
              mount.  Without this<br>
              > change, any files created by a Win32 process outside
              of Cygwin will<br>
              > result in Cygwin having no permissions to do anything
              with the files.<br>
              > <a moz-do-not-send="true"
href="http://georgik.sinusgear.com/2012/07/14/how-to-fix-incorrect-cygwin-permission-inwindows-7/"
                target="_blank">http://georgik.sinusgear.com/2012/07/14/how-to-fix-incorrect-cygwin-permission-inwindows-7/</a><br>
              ><br>
              <br>
            </div>
            Thanks, I'll have a look and see if that addresses the issue
            I was<br>
            seeing with having /usr/local mounting during the build.<br>
            <br>
            Regards, Alex<br>
            <div class="HOEnZb">
              <div class="h5"><br>
                _______________________________________________<br>
                Mono-devel-list mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:Mono-devel-list@lists.ximian.com">Mono-devel-list@lists.ximian.com</a><br>
                <a moz-do-not-send="true"
                  href="http://lists.ximian.com/mailman/listinfo/mono-devel-list"
                  target="_blank">http://lists.ximian.com/mailman/listinfo/mono-devel-list</a><br>
              </div>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>