From: Joel Soete <soete.joel@tiscali.be>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] glibc cvs: additional patche
Date: Sun, 07 Mar 2004 13:05:27 +0000 [thread overview]
Message-ID: <404B1E17.6020004@tiscali.be> (raw)
Hi Carlos,
Since yesterday cvs update, i also need a patch similar to:
<http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/sysdeps/s390/s390-32/dl-machine.h.diff?r1=1.19&r2=1.20&cvsroot=glibc>
=========><=========
--- sysdeps/hppa/dl-machine.h.orig 2004-03-07 12:26:36.000000000 +0100
+++ sysdeps/hppa/dl-machine.h 2004-03-07 12:34:06.000000000 +0100
@@ -252,7 +252,7 @@
}
else
{
- if (_dl_name_match_p (GL(dl_profile), l))
+ if (_dl_name_match_p (GLRO(dl_profile), l))
{
/* This is the object we are looking for. Say that
we really want profiling and the timers are
@@ -581,9 +581,9 @@
static inline void __attribute__ ((unused))
dl_platform_init (void)
{
- if (GL(dl_platform) != NULL && *GL(dl_platform) == '\0')
+ if (GLRO(dl_platform) != NULL && *GLRO(dl_platform) == '\0')
/* Avoid an empty string which would disturb us. */
- GL(dl_platform) = NULL;
+ GLRO(dl_platform) = NULL;
}
#endif /* !dl_machine_h */
@@ -684,7 +684,7 @@
break;
if (__builtin_expect (sym->st_size > refsym->st_size, 0)
|| (__builtin_expect (sym->st_size < refsym->st_size, 0)
- && __builtin_expect (GL(dl_verbose), 0)))
+ && __builtin_expect (GLRO(dl_verbose), 0)))
{
const char *strtab;
=========><=========
hth,
Joel
next reply other threads:[~2004-03-07 13:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 13:05 Joel Soete [this message]
2004-03-07 21:23 ` [parisc-linux] Re: glibc cvs: additional patche Carlos O'Donell
2004-03-08 7:27 ` Joel Soete
2004-03-08 17:49 ` [parisc-linux] New glibc patches 2004-03-08, fixes GLRO changes Carlos O'Donell
2004-03-09 9:04 ` [parisc-linux] " Joel Soete
2004-03-09 13:49 ` Joel Soete
2004-03-09 15:03 ` Carlos O'Donell
2004-03-09 15:41 ` Joel Soete
2004-03-10 14:47 ` Joel Soete
2004-03-10 18:21 ` Joel Soete
2004-03-11 18:42 ` Carlos O'Donell
2004-03-12 15:32 ` Joel Soete
2004-03-12 16:41 ` Carlos O'Donell
2004-03-12 17:33 ` Joel Soete
2004-03-12 21:20 ` Carlos O'Donell
2004-03-13 18:59 ` Joel Soete
2004-03-14 19:32 ` Carlos O'Donell
2004-03-14 19:40 ` Carlos O'Donell
2004-03-14 19:59 ` Joel Soete
2004-03-14 20:12 ` James Morrison
2004-03-15 6:31 ` Joel Soete
2004-03-16 14:57 ` James Morrison
2004-03-15 17:38 ` Joel Soete
2004-03-15 18:51 ` Carlos O'Donell
2004-03-16 9:43 ` Joel Soete
2004-03-16 21:09 ` Carlos O'Donell
2004-03-17 8:30 ` Joel Soete
2004-03-18 17:59 ` Carlos O'Donell
2004-03-23 7:07 ` Joel Soete
2004-03-23 17:06 ` Carlos O'Donell
2004-04-01 15:14 ` Joel Soete
2004-04-02 5:51 ` Carlos O'Donell
2004-03-09 15:07 ` James Morrison
2004-03-09 15:09 ` Carlos O'Donell
2004-03-09 15:39 ` James Morrison
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=404B1E17.6020004@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=carlos@baldric.uwo.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox