Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: hppa glibc 2.3.3
Date: Sun, 10 Oct 2004 21:44:09 -0700	[thread overview]
Message-ID: <20041011044409.GW14151@tausq.org> (raw)
In-Reply-To: <20041008170106.GW24430@baldric.uwo.ca>

> The only problem might exist if __errno_location does not return the
> proper address of rltd_errno when RTLD_PRIVATE_ERRNO is defined. It
> should. If it doesn't then our definition of
> SYSCALL_ERRNO_HANDLER should change in that situation (away from
> DEFAULT_SYSCALL_ERROR_HANDLER which is set to __errno_location).

is there a fix for this? i was building glibc from cvs today to look at
the _dl_debug_state problem and ran into this too.... (also the problem
with the missing NULL defn for waitid)

The problem here seems to be that we are using the generic dl-sysdep.h 
and errno.c/errno-loc.c definitions, and when building rtld-errno-loc.o,
__errno_location is coded to return &errno and not &rtld_errno.

i hacked this in my build but not sure if this is the proper solution --
should we propose a change to the generic errno-loc.c? or do we need our
own? or am i on the wrong track?

i'm using something like this:

Index: linuxthreads/sysdeps/pthread/errno-loc.c
===================================================================
RCS file: /cvs/glibc/libc/linuxthreads/sysdeps/pthread/errno-loc.c,v
retrieving revision 1.3
diff -u -p -r1.3 errno-loc.c
--- linuxthreads/sysdeps/pthread/errno-loc.c	1 Apr 2003 00:52:40 -0000	1.3
+++ linuxthreads/sysdeps/pthread/errno-loc.c	11 Oct 2004 04:41:14 -0000
@@ -24,9 +24,13 @@
 #include <sysdep-cancel.h>
 
 #if ! USE___THREAD
+#if RTLD_PRIVATE_ERRNO
+extern int rtld_errno;
+#else
 #undef errno
 extern int errno;
 #endif
+#endif
 
 int *
 #if ! USE___THREAD
@@ -41,6 +45,10 @@ __errno_location (void)
       return LIBC_THREAD_GETMEM (self, p_errnop);
     }
 #endif
+#if RTLD_PRIVATE_ERRNO
+  return &rtld_errno;
+#else
   return &errno;
+#endif
 }
 libc_hidden_def (__errno_location)

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2004-10-11  4:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08  6:00 [parisc-linux] Re: hppa glibc 2.3.3 Joel Soete
2004-10-08 17:01 ` Carlos O'Donell
2004-10-11  4:44   ` Randolph Chung [this message]
2004-10-12 20:38     ` Carlos O'Donell
     [not found] <200409271755.i8RHtNoa017851@hiauly1.hia.nrc.ca>
     [not found] ` <Pine.LNX.4.58.0409272134390.422@trillian.uni>
     [not found]   ` <20040928032200.GF27033@baldric.uwo.ca>
     [not found]     ` <Pine.LNX.4.58.0410050846320.924@trillian.uni>
2004-10-06  4:56       ` Carlos O'Donell
     [not found]         ` <4161729B00001345@mail-1-bnl.tiscali.it>
2004-10-07 15:29           ` Carlos O'Donell
2004-10-07 16:08             ` Joel Soete
2004-10-07 17:03               ` Joel Soete
2004-10-07 22:39                 ` Carlos O'Donell

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=20041011044409.GW14151@tausq.org \
    --to=randolph@tausq.org \
    --cc=carlos@baldric.uwo.ca \
    --cc=parisc-linux@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