[MonoDevelop] Failing to build from git
Jonathan Ballard
dzonatas at gmail.com
Mon Oct 29 23:54:04 UTC 2012
Debian's apt-get often shows, likewise, the err... on mono packages, for
"imported assemblies." {info:}
It happens when compilers and linkers do not agree. Try LLVM at least for
its added dependency.
It would be kind of "token" for the workaround if it resolves this issue
upstream easier than force upgrade, which is where the confusion starts
between the two corporations in their assembled code. Some people compile
an entire new system every upgrade, so the cherry-pick method seems
out-dated when that still requires completion dialogue. In debian,
the committees could depend on LLVM instead of mono packages, and update
mono packages to use deb-src directly for assembly (except for the
/bin/mono shell installation). Better should be to allow the choice between
LLVM(pipe) or mono shell, upgrade(_t).
Thanks for this reflection. {asm:}
On Sunday, October 28, 2012, Matt Calder wrote:
> Alan,
>
> I built the latest mono:
>
> calder at goat:~/tmp/mono-addins$ mono --version
> Mono JIT compiler version 3.0.1 (master/7a59454 Sun Oct 28 13:49:57 EDT
> 2012)
> Copyright (C) 2002-2012 Novell, Inc, Xamarin Inc and Contributors.
> www.mono-project.com
> TLS: __thread
> SIGSEGV: altstack
> Notifications: epoll
> Architecture: amd64
> Disabled: none
> Misc: softdebug
> LLVM: supported, not enabled.
> GC: Included Boehm (with typed GC and Parallel Mark)
>
> running configure in the monodevelop clone directory fails:
>
> checking for GLADE_SHARP... yes
> checking for MONODOC... yes
> checking for GNOME_SHARP... no
> checking for GNOME_VFS_SHARP... no
> checking for GCONF_SHARP... no
> configure: error: Cannot enable GNOME platform without gnome-sharp-2.0
> make[1]: *** [config.status] Error 1
> make[1]: Leaving directory `/home/calder/tmp/monodevelop/main'
> make: *** [all-recursive] Error 1
>
> I tried to build gnome-sharp, but its make fails (full output attached):
>
> /usr/lib/mono/4.5/mscorlib.dll (Location of the symbol related to previous
> warning)
> error CS1705: Assembly `gdk-sharp, Version=2.12.0.0, Culture=neutral,
> PublicKeyToken=35e10195dab3c99f' references `Mono.Cairo, Version=4.0.0.0,
> Culture=neutral, PublicKeyToken=0738eb9f132ed756' which has a higher
> version number than imported assembly `Mono.Cairo, Version=2.0.0.0,
> Culture=neutral, PublicKeyToken=0738eb9f132ed756'
> Compilation failed: 1 error(s), 3 warnings
>
> This is pretty frustrating, as I mentioned previously I regularly build
> from source on my desktop without issues. Thanks for any help on this,
>
> Matt
>
>
>
> On Sat, Oct 27, 2012 at 6:39 PM, Alan <alan.mcgovern at gmail.com> wrote:
>
> Git submodules have nothing to do with autoconf etc. The only reason
> for making Mono.Addins a submodule is that we needed fixes which only
> existed in git master of Mono.Addins and this was the best way we
> could get those fixes released on all supported platforms
> simultaenously.
>
> Could you export these two environment variables and then try another
> build. Then attach the output to an email so we can diagnose the
> issue. It's quite possible the issue would go away if you used a newer
> version of mono.
>
> export MONO_LOG_LEVEL=info
> export MONO_LOG_MASK=asm
>
> Alan
>
> On 27 October 2012 18:30, Jonathan Ballard <dzonatas at gmail.com> wrote:
> > If you don't mind GPL then, try this version:
> >
> > http://www.gnu.org/software/autoconf/
> >
> >
> > $ configure --prefix=GIT:/
> >
> > Or; logically, "[i]::CLSID_" instead of /usr/... in ECMAScript, which
> mono
> > could include submodules as resources upon the build of configure.exe.
> >
> > See also: man(stable:1), schroot(sid:3).
> >
> >
> > On Saturday, October 27, 2012, Jonathan Ballard wrote:
> >>
> >> Submodules are OK, but the "submodule update --init" seems only needed
> if
> >> there are absolute paths. I see you used "--prefix", so there is this
> >> secondary level of indirection that may confuse any intention that
> exists.
> >>
> >> I guess that is why developers dropped the autotools ("configure")
> package
> >> when git has "the better way" built-in.
> >>
> >> On Saturday, October 27, 2012, Matt Calder wrote:
> >>>
> >>> I routinely build mono + monodevelop from source on my desktop.
> However,
> >>> I have been unable, despite several hours of trying over several days,
> to
> >>> build monodevelop on a new laptop. I installed mono without issue. I
> cloned
> >>> monodevelop and ran:
> >>>
> >>> git submodule update --init --recursive
> >>>
> >>> then
> >>>
> >>> ./configure --prefix=/usr
> >>>
> >>> and get:
> >>>
> >>> ...
> >>> checking for MONO_ADDINS... no
> >>> configure: error: Package requirements (mono-addins >= 0.6) were not
> met:
> >>>
> >>> I cloned the mono-addins project (though I thought the git submodule
> >>> business was supposed to remove the need for this), but that fails
> during
> >>> make with:
> >>>
> >>> Can't find custom attr constructor image:
> >>>
> /usr/lib/mono/gac/Microsoft.Build.Tasks.v4.0/4.0.0.0__b03f5f7f11d50a3a/Microsoft.Build.Tasks.v4.0.dll
> >>> mtoken: 0x0a0001ef
> >>> : error : Error initializing task Message: Exception has been thrown by
> >>> the target of an invocation.
> >>>
> >>> I have exhausted my repetoire of tricks and would appreciate any help
> on
> >>> this. My system is:
> >>>
> >>> calder at goat:~/tmp/mono-addins$ mono --version
> >>> Mono JIT compiler version 2.10.8.1 (Debian 2.10.8.1-1ubuntu2.2)
> >>> Copyright (C) 2002-2011 Novell, Inc, Xamarin, Inc and Contributors.
> >>> www.mono-project.com
> >>> TLS: __thread
> >>> SIGSEGV: altstack
> >>> Notifications: epoll
> >>> Architecture: amd64
> >>> Disabled: none
> >>> Misc: softdebug
> >>> LLVM: supported, not enabled.
> >>> GC: Included Boehm (with typed GC and Parallel Mark)
> >>> calder at goat:~/tmp/mono-addins$
> >>> calder at goat:~/tmp/mono-addins$ uname -a
> >>> Linux goat 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012
> >>> x86_64 x86_64 x86_64 GNU/Linux
> >>>
> >>> Thanks,
> >>>
> >>> Matt
> >>>
> >
> >
> > _______________________________________________
> > Monodevelop-list mailing list
> > Monodevelop-list at lists.ximian.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/monodevelop-list/attachments/20121029/97da2e30/attachment.html>
More information about the Monodevelop-list
mailing list