[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#668794: reopen

severity 668794 important
forwarded 668794 http://code.google.com/p/go/issues/detail?id=3533
thank you

Hi Robert,

(sorry for BTS juggling, I found your comment just after I sent the
first email.)

Anyway I agree that the problem needs to be fixed upstream, but I would suggest
that we keep GNU/KFreeBSD build enabled for the moment and if this cannot be
fixed before freeze, we can always disable it. It would be shame to disable this
build right now, because there would be basically no push to make it
work (if there
is more stuff broken than just the tests).

Thus I am downgrading the severity to important, so it doesn't block
transition, and
will take care of GNU/KFreeBSD builds somewhere around June.

Is that ok with you?


On Mon, Apr 16, 2012 at 00:04, Robert Millan <rmh@debian.org> wrote:
> found 668794 2:1-4
> thanks
> Hi Ondřej,
> I notice you disabled the golang testsuite because it hangs on
> GNU/kFreeBSD.  However, the problem is still present, and chances are
> it makes golang unusable on that platform.
> I gave the source a look, and it seems that on GNU/kFreeBSD golang is
> playing with thread primitives, bypassing libc.  For example it
> invokes thr_new() kernel call directly, and also calls sigprocmask()
> to reset the signal mask in code that is clearly multithreaded [1].
> This means that either golang intends to completely replace
> libpthread, or it intends to play along with existing libpthread.  I'm
> not sure which one applies here, but in both cases there is a problem
> that needs to be fixed in golang.
> So please don't disable the testsuite.  If golang can't be built on
> GNU/kFreeBSD, unless you know it's a bug in the system libraries the
> problem needs to be fixed in golang.  If nobody can spend the time to
> fix it here, then you should consider not providing the package for
> kfreebsd-*.
> [1] On multithreaded programs, use of sigprocmask() is reserved to
> system libraries.
> --
> Robert Millan

Ondřej Surý <ondrej@sury.org>

Reply to: