Re: mono-devel >= 2.0 vs /usr/bin/csc
On Wed, 2009-06-24 at 18:19 +0200, Mathieu Malaterre wrote:
> 'lo there,
>
> So once again I copied the debian/* files from gmime2.4 and again
> this is not working for me:
>
> https://buildd.debian.org/~luk/status/package.php?p=gdcm
>
> gdcm/i386 tail of last log:
> ...
> /build/buildd-gdcm_2.0.10-6-i386-8AnMbf/gdcm-2.0.10/Source/MediaStorageAndFileFormat/gdcmSplitMosaicFilter.h:52:
> Warning(516): Overloaded method gdcm::SplitMosaicFilter::GetFile()
> const ignored. Method gdcm::SplitMosaicFilter::GetFile() at
> /build/buildd-gdcm_2.0.10-6-i386-8AnMbf/gdcm-2.0.10/Source/MediaStorageAndFileFormat/gdcmSplitMosaicFilter.h:51
> used.
> [ 96%] csc *.cs
> /bin/sh: /usr/bin/csc: No such file or directory
> make[3]: *** [bin/./gdcm_csharp.dll] Error 127
>
>
> Why is ok in gmime2.4 to:
>
> Build-Depends-Indep: cli-common-dev (>= 0.5.7),
> mono-devel (>= 2.0),
>
> but not in my package...
>
> mono-devel should provide /usr/bin/csc right ?
Yes, /usr/bin/csc is in mono-devel.
You're not trying to call csc from your build-arch rule are you?
Reply to: