[Pkg-mono-devel] Problems building from source package

[Mirco Bauer]

Hi,

sorry for my late reply

On Mon, 2005-10-03 at 14:46 +1300, Will Bryant wrote:
> Hi guys,
> 
> I tried compiling 1.1.9 from the source package from
> http://people.debian.org/~formorer/mono on my previously mono-less
> sarge box, and got the following:
>         [...]
>         debian/dh_makeclilibs -i -m 1.0 internal-mono
>         dh_makeclilibs: Warning! No Build-Depends(-Indep) on
>         cli-common (>= 0.2.0)!
>         dh_makeclilibs:
>         MONO_PATH=debian/tmp/usr/lib/mono/1.0:debian/tmp/usr/lib/mono/2.0 debian/tmp/usr/bin/monodis could not open debian/mono-classlib-1.0/usr/lib/mono/gac/Accessibility/1.0.5000.0__b03f5f7f11d50a3a/Accessibility.dll, maybe some components not installed yet. Using filename to guess the assembly name :(
>         dh_makeclilibs:
>         MONO_PATH=debian/tmp/usr/lib/mono/1.0:debian/tmp/usr/lib/mono/2.0 debian/tmp/usr/bin/monodis could not open debian/mono-classlib-1.0/usr/lib/mono/gac/Commons.Xml.Relaxng/1.0.5000.0__0738eb9f132ed756/Commons.Xml.Relaxng.dll, maybe some components not installed yet. Using filename to guess the assembly name :(
>         [dozens more]
> 

this was solved in Mono 1.1.9.1-3, known FTBFS

> Installing the cli-common package before building resolved the
> problem, but of course a number of other packages were installed as
> well to satisfy its dependencies; working backwards and removing them
> one by one, it seems that the necessary package is libmono0.
> 
> I don't know anything about the Debian mono packages, but looking the
> commands above it appears to me that the source package *should* be
> buildable without other packages; is that expected to be the case, or
> are we just missing a build-dependency?

all source packages must be buidable by calling debian/rules binary

> 
> FWIW, the files that it's complaining about, for example
> "debian/mono-classlib-1.0/usr/lib/mono/gac/Accessibility/1.0.5000.0__b03f5f7f11d50a3a/Accessibility.dll" in the errors above, do actually exist (and are readable), so it's not that their build failed - it's dh_makeclilibs that doesn't seem to be working correctly. "debian/tmp/usr/lib/mono/1.0" and

thats because monodis doesn't work right, caused by a missing
LD_LIBRARY_PATH

>  "debian/tmp/usr/lib/mono/2.0" also exist, and seem filled with
> suitable assembly goodness, though I do notice that the .config file
> links are broken - ../gac contains .dll files and the
> corresponding .dll.mdb files, but no .dll.config files - but it looks
> like that's normal, since it's that way in the installed packages too?

those dangling symlinks are an upstream bug and already fixed upstream,
it's harmless.

-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key:
http://keyserver.noreply.org/pks/lookup?op=get&search=0xEEF946C8

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT d s-:+ a-- C++ UL++++$ P L++$>+++$ E- W+++$ N o? K- w++>! O---- M-
V? PS
PE+ Y- PGP++ t 5+ X++ R tv+ b+ DI? D+ G>++ e h! r->++ y?
------END GEEK CODE BLOCK------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-mono-devel/attachments/20051012/3eb66658/attachment.pgp