From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] INTERNAL_SYSCALL_NCS for SH
Date: Thu, 23 Sep 2004 23:25:00 -0000 [thread overview]
Message-ID: <20040924.082440.116352926.kkojima@rr.iij4u.or.jp> (raw)
In-Reply-To: <20040924.075227.35012688.kkojima@rr.iij4u.or.jp>
>> BTW, SH port has a few problems with setXid changes. I'll report
>> them in the next mail.
>
> SH uses the old-fashioned 16-bit id's. It causes a few problems with
> setXid changes. The first problem is that seteuid.c and setegid.c may
> call __setre*[ug]id and causes undefined references. It seems pthread
> cases should use pthread_setre*[ug]id_np instead of __setre*[ug]id.
>
> The second one is that the variable __libc_missing_32bit_uids is defined
> in getuid.c but we don't have pthread_getuid. I've added an SH specific
> pthread_getuid as a workaround. I'd like to append a patch I'm using
> for comments.
Ugh. Please ignore this mail. I didn't noticed that some setXid changes
have been removed. I'll update my tree and try again. Sorry for the noise.
Regards,
kaz
next prev parent reply other threads:[~2004-09-23 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 22:43 Kaz Kojima
2004-09-23 22:52 ` Kaz Kojima
2004-09-23 23:25 ` Kaz Kojima [this message]
2004-09-24 1:22 ` Kaz Kojima
2004-09-24 6:20 ` Ulrich Drepper
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=20040924.082440.116352926.kkojima@rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=libc-hacker@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).