From: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>
To: Matthew Wilcox <willy@debian.org>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] new glibc dpatch
Date: Wed, 17 Oct 2001 00:14:53 -0400 [thread overview]
Message-ID: <20011017001453.A11826@megatonmonkey.net> (raw)
In-Reply-To: <20011017004218.K15532@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Wed, Oct 17, 2001 at 12:42:18AM +0100
>
> due to a few people hassling me, i've created a new hppa patch for glibc.
> it incorporates a couple of changes Carlos posted to the list and adds a
> couple of diffs of my own. i've sent it to BenC for the 2.2.4-4 release
> of glibc, which he assures me is imminent.
>
That's my name!
> You can find it at
> ftp://puffin.external.hp.com/pub/parisc/src/glibc22-hppa.dpatch
>
> have fun. it's still building on paer.d.o, but i would expect it to
> fail to build in the same place as before.
Looking through the patch changes and comparing to mine.
(The build has begun)
Just a comment about your changes to ./sysdeps/ia64/dl-fptr.c
=====
--- glibc22-hppa.dpatch Tue Oct 16 20:52:02 2001
+++ glibc22-hppa.dpatch.mw Tue Oct 16 21:05:27 2001
@@ -1135,7 +1135,7 @@
unsigned int npages; /* # of pages to allocate */
#ifdef _LIBC_REENTRANT
- volatile int lock;
-+ __atomic_lock_t lock;
++ static __atomic_lock_t lock = __ATOMIC_LOCK_INIT;
sigset_t full_sigset;
#endif
/* the next to members MUST be consecutive! */
=====
Should the lock be static and initialized? Comment?
c.
next prev parent reply other threads:[~2001-10-17 4:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 23:42 [parisc-linux] new glibc dpatch Matthew Wilcox
2001-10-17 4:14 ` Carlos O'Donell Jr. [this message]
2001-10-17 4:35 ` Matthew Wilcox
2001-10-17 4:55 ` Carlos O'Donell Jr.
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=20011017001453.A11826@megatonmonkey.net \
--to=carlos@megatonmonkey.net \
--cc=parisc-linux@parisc-linux.org \
--cc=willy@debian.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.