[Pkg-giraffe-maintainers] Bug#875456: libvmime: FTBFS on non-Linux: no getThreadId implementation

[Carsten Schoenert]

Hello Aaron,

On Tue, Sep 12, 2017 at 09:12:40PM -0400, Aaron M. Ucko wrote:
> "Aaron M. Ucko" <ucko at debian.org> writes:
> 
> >   /«PKGBUILDDIR»/src/vmime/platforms/posix/posixHandler.cpp:243:3: error: #error We have no implementation of getThreadId() for this platform!
> 
> Thanks for the quick fix!

well, I had prepared the now used patch for quite a while but haven't
done a new upload since then, so no real quick working on that to be
fare. But while working on kopanocore it was worth to do a new shot on
libvmime.
There was a bug report [1] about build issues for libvmime on *BSD while
working on that patch, but upstream hasn't implemented anything yet that
could solve this. Later on, (as seen yesterday) a probably better
solution than the patch I've used has been added [2]. But I'm not sure
if this solve the build problem that still exist on Hurd.

>  Alas, the Hurd build still failed because
> Mach has its own API for this functionality:
> 
>   /<<PKGBUILDDIR>>/src/vmime/platforms/posix/posixHandler.cpp:244:12: error: 'SYS_thr_self' was not declared in this scope
> 
> It looks like it should work to call mach_thread_self() from
> <mach/mach_traps.h>.  However, please bear in mind that you'll
> then need to pass the result to mach_port_deallocate per
> https://bugs.launchpad.net/sbcl/+bug/723581 .

I have no great experience about this specific mechanism no matter what
platform on. I appreciate any help from porters here, due the
specialities of Hurd and the current state in Debian I wont spend much
time for working on that.

Maybe I give it a try on a porterbox after adding the upstream fix.

[1] https://github.com/kisli/vmime/issues/177
[2] https://github.com/kisli/vmime/commit/243efb267fe539958610ef1e2142a36dfbcd3c28

Regards
Carsten