All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] testandset
Date: Fri, 21 Sep 2001 11:58:40 -0400	[thread overview]
Message-ID: <20010921115840.C25803@megatonmonkey.net> (raw)

> 
> because we're removing the testandset macro, replacing it with try_lock.
> 

Noted.

> > e) Packed it all back up as tar.bz2 (./debian rules seems to call for this)
> 
> No, definitely not, I don't know why you think you need to do that.
> 

Thus my belief that I'm using the dpkg-dev tools wrong.
I read the docs late at night... maybe I didn't read them at all,
maybe I just dreamt that I did? ;)

> dpkg-source -x *dsc
> cd glibc-*
> frob 0lists & hppa.dpatch as above
> put a copy of the kernel includes in /usr/src/linux/include rather than setting
> LINUX_SOURCE
> dpkg-buildpackage -B -a -rfakeroot

I will give it another go (I've done a few compiles already).

My 712/60 is painfully slow :} 
Any recommendations for a faster machine?

We're almost to the point of setting up (Paul is looking at it)
pmake to build glibc. Hey, we've got a cluster for a reason.

Has anyone on this list used fai with hppa on this list?
http://www.informatik.uni-koeln.de/fai/.
(Hrm.. I'll post to beowulf@beowulf.org)

c.

             reply	other threads:[~2001-09-21 15:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-21 15:58 Carlos O'Donell Jr. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-21 15:37 [parisc-linux] testandset Carlos O'Donell Jr.
2001-09-21 15:42 ` Matthew Wilcox
2001-09-21 16:10   ` Carlos O'Donell Jr.
2001-09-21  1:12 Carlos O'Donell Jr.
2001-09-21 15:17 ` Matthew Wilcox

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=20010921115840.C25803@megatonmonkey.net \
    --to=carlos@megatonmonkey.net \
    --cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.