linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: DB_THREAD support in Berkeley DB/glibc
Date: Tue, 28 Dec 1999 02:59:01 -0500	[thread overview]
Message-ID: <19991228025900.A1950@drow.res.cmu.edu> (raw)
In-Reply-To: <Pine.LNX.4.10.9912262058050.21529-100000@altus.drgw.net>; from hozer@drgw.net on Sun, Dec 26, 1999 at 09:04:12PM -0600


If I'm not mistaken, David Huggins-Daines did this recently.  It is in
the debian packages of glibc in the latest release.


On Sun, Dec 26, 1999 at 09:04:12PM -0600, Troy Benjegerdes wrote:
> 
> I've just figured out that the reason openldap doesn't work is that it
> assumes all platforms support the DB_THREAD argument for db_appinit.
> 
> After looking at the glibc/Berkeley DB source, it turns out that all it
> needs is 10 or so lines of ASM for spinlocks.
> 
> Could someone working on glibc developement add the required ASM and get
> this into the mainline distribution? Thanks.
> 
> (look in glibc/db2/mutex, I believe )
> 
> --------------------------------------------------------------------------
> | Troy Benjegerdes    |  troy@blacklablinux.com    |    hozer@drgw.net   |
> |    Unix is user friendly... You just have to be friendly to it first.  |
> | This message composed with 100% free software.    http://www.gnu.org   |
> --------------------------------------------------------------------------
> 
> 


Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-12-28  7:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-27  3:04 DB_THREAD support in Berkeley DB/glibc Troy Benjegerdes
1999-12-28  7:59 ` Daniel Jacobowitz [this message]
1999-12-28 17:53   ` Joel Klecker
1999-12-28 19:02     ` David Edelsohn
1999-12-28 21:22       ` BenH
1999-12-28 22:05       ` Daniel Jacobowitz
1999-12-28 22:28         ` David Edelsohn
1999-12-28 23:21           ` Tony Mantler
1999-12-29  0:15             ` David Edelsohn
1999-12-29  0:54               ` Geoff Keating
1999-12-29  1:01                 ` David Edelsohn
1999-12-28 23:52           ` Geoff Keating
1999-12-29  0:21             ` David Edelsohn
  -- strict thread matches above, loose matches on Subject: below --
1999-05-10 23:59 imac of booting Ben Martz
1999-05-11  8:36 ` Joel Klecker
1999-05-11 15:22   ` David Edelsohn
1999-05-11 16:47     ` Geert Uytterhoeven
1999-05-11 17:44     ` Anyone playing with Darwin 0.2 binary yet? Kevin B. Hendricks
1999-05-11 18:47       ` Nathan Ingersoll
1999-05-11 21:00         ` Roger Ivie
1999-05-11 22:15           ` David A. Gatwood
     [not found]         ` <v04011701b35e71c158ed@[199.174.98.46]>
1999-05-12 14:50           ` New PPC/Mac features of 2.2.8? Jason Haas
1999-05-12 18:21             ` Matt Porter
1999-05-12 19:41             ` Tom Rini

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=19991228025900.A1950@drow.res.cmu.edu \
    --to=drow@false.org \
    --cc=linuxppc-dev@lists.linuxppc.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).