git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Brandenburg <randy.brandenburg@woh.rr.com>
To: git@vger.kernel.org
Subject: Re: Unable to fork off sideband demultiplexer
Date: Fri, 3 Jun 2011 13:30:00 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110603T151012-143@post.gmane.org> (raw)
In-Reply-To: 20110602192927.GA21262@sigill.intra.peff.net

Jeff King <peff <at> peff.net> writes:

> Great, I'm glad it's working. With NO_PTHREADS set, you will be
> fork()ing off the sideband process instead of using a thread. So you
> avoid pthreads altogether and it works, but you can't do multi-threaded
> delta compression.
> 
> If you build without NO_PTHREADS set on a Solaris 9 box, does it work on
> that same box? That would confirm or deny my ABI compatibility theory
> (and hopefully point us in the right direction for the sunfreeware
> people to build a binary that works on Solaris 9 and 10).
> 

Building without NO_PTHREADS set results in the original "broken" behaviour. I 
am staying with the working version in the interest of time. May investigate 
more later. 

Thanks for all the insight and tips.

- Randy

  parent reply	other threads:[~2011-06-03 13:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 14:16 Unable to fork off sideband demultiplexer Randy Brandenburg
2011-06-01 17:15 ` Junio C Hamano
2011-06-01 17:35   ` Jeff King
2011-06-01 19:10     ` Randy Brandenburg
2011-06-02 15:29       ` Randy Brandenburg
2011-06-02 19:29         ` Jeff King
2011-06-03 12:32           ` Randy Brandenburg
2011-06-03 13:30           ` Randy Brandenburg [this message]
2011-06-03 14:49             ` Jeff King
2011-06-03 18:52               ` Randy Brandenburg
2011-06-03 19:24                 ` Jeff King
2011-06-03 22:18               ` Brandon Casey
2011-06-02 19:36 ` Ben Walton
2011-06-03 12:29   ` Randy Brandenburg
2011-06-04 19:32     ` Ben Walton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20110603T151012-143@post.gmane.org \
    --to=randy.brandenburg@woh.rr.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).