Source: zeromq3
Version: 4.0.5+dfsg-2
Severity: Important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
Attached are patches for adding GNU/Hurd to the list of supported
architectures for zeromq3. I have tried bot the select and poll
versions, same result.
Libraries needed to run
* libshouldbeinlibc/assert-backtrace.h: New file.
* libshouldbeinlibc/Makefile (installhdrs): Add assert-backtrace.h.
---
libshouldbeinlibc/Makefile | 4 ++-
libshouldbeinlibc/assert-backtrace.h | 68
2 files changed, 71 insertions(+), 1 deletion(-)
* include/refcount.h: Use assert-backtrace.h.
---
include/refcount.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/refcount.h b/include/refcount.h
index ebde42d..5bb9660 100644
--- a/include/refcount.h
+++ b/include/refcount.h
@@ -22,7 +22,7 @@
#ifndef _HURD_REFCOUNT
Hello,
for reference, here is the patch. I'm not sure how to properly
integrate this.
Justus
Quoting Richard Braun (2014-10-28 17:59:16)
> On Tue, Oct 28, 2014 at 01:37:43AM +0100, Justus Winter wrote:
> > Preliminary testing on my box as well as on darnassus looks promising
> > (modulo some pfinet weirdness that Richard is investigating [and imho
> > if there is an issue, it should be unr
Hello :)
Quoting Samuel Thibault (2014-10-06 11:30:26)
> Thomas Schwinge, le Mon 06 Oct 2014 11:22:50 +0200, a écrit :
> > So, anything specific that we should wait for before bundling the next
> > release snapshots?
>
> It'd be nice to include the init->startup series after review. (I'm OK
> wit
On Tue, Oct 28, 2014 at 01:37:43AM +0100, Justus Winter wrote:
> Preliminary testing on my box as well as on darnassus looks promising
> (modulo some pfinet weirdness that Richard is investigating [and imho
> if there is an issue, it should be unrelated to this change]). We
> will keep you posted.
On Tue, Oct 28, 2014 at 01:37:43AM +0100, Justus Winter wrote:
> Preliminary testing on my box as well as on darnassus looks promising
> (modulo some pfinet weirdness that Richard is investigating [and imho
> if there is an issue, it should be unrelated to this change]). We
> will keep you posted.