Re: gdcm: Got a SIGABRT while executing native code
On Sat, May 30, 2009 at 4:00 PM, Mathieu Malaterre
<mathieu.malaterre@gmail.com> wrote:
> On Sat, May 30, 2009 at 11:48 AM, Mirco Bauer <meebey@debian.org> wrote:
> ...
>> That it freaks out like this is probably a bug, not sure if SIGABRT is
>> ok for expected fatal conditions.
>>
>> The issue is that some (but not all) buildds do not have a writable
>> home-directory. The Mono runtime is emulating some I/O features that
>> Microsoft .NET supports using that .wapi directory in $HOME. Most
>> applications don't need this emulation though, so either the emulation
>> should be disabled or a writable home-directory set. This common issue
>> is also mentioned in the Debian CLI Policy §4.3 [0]
>>
>> The recommended version is now to disable it using:
>> export MONO_DISABLE_SHM=1
>
> I do not understand what this means. Do you want me to add the
> previous export to the debian/rules file for gdcm ?
>
>
>> One related note, I did a short check of the gdcm source packages and
>
> Cool ! Thanks for taking the time !
>
>> noticed it doesn't handle "Mono architectures". Mono is not available
>> for all Debian architectures. It supports all except: m68k, hppa and
>> alpha. This means your Build-Depends line has to cope with that, to
>> only pull the mono deps in when it's a Mono arch. At the same time the
>> configure script/call has to optionally skip the building of the Mono
>> binding, else it will FTBFS on the named unsupported archs.
>
> I am looking at:
>
> http://pkg-mono.alioth.debian.org/cli-policy/ch-packaging.html#s-build-deps
>
> Do you have a reference on how to do that ?
Should I hardcode which architecture does not work:
Build-Depends: mono-devel (>= 2.0) [!alpha !hppa !m68k]
Thanks,
--
Mathieu
Reply to: