From: Alexandre Oliva <aoliva@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: Fix _exit for Linux
Date: Mon, 16 Sep 2002 09:46:00 -0000 [thread overview]
Message-ID: <or1y7uxa5v.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <u8lm62bo1p.fsf@gromit.moeb>
On Sep 16, 2002, Andreas Jaeger <aj@suse.de> wrote:
> +libc_hidden_def (_exit)
Hmm. I don't think this is right. libc_hidden_proto (_exit) is
commented out in include/unistd.h, so, if my understanding is correct,
libc_hidden_def (_exit) is not guaranteed to have the right effect.
In fact, it fails to link libc.so on mips-linux, not only because
_exit ends up undefined, but also because INLINE_SYSCALL has no
arch-specific definition on mips, and we end up with a call to
__syscall_exit, that does not exist. I've tweaked the syscall file
such that a definition for __syscall_exit is generated, but this was
not enough to get _exit() to be defined, so the link of libc.so still
failed.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-09-16 16:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 20:40 Andreas Jaeger
2002-09-15 22:11 ` Ulrich Drepper
2002-09-15 23:56 ` Roland McGrath
2002-09-16 0:10 ` Ulrich Drepper
2002-09-16 0:36 ` Roland McGrath
2002-09-16 0:45 ` Ulrich Drepper
2002-09-16 9:46 ` Alexandre Oliva [this message]
2002-09-16 9:37 ` Andreas Jaeger
2002-09-16 9:52 ` Alexandre Oliva
2002-09-16 9:54 ` Jakub Jelinek
2002-09-16 10:14 ` Ulrich Drepper
2002-09-24 20:24 ` Alexandre Oliva
2002-09-24 20:28 ` Roland McGrath
2002-09-24 20:35 ` Ulrich Drepper
2002-09-24 21:08 ` Roland McGrath
2002-09-24 21:53 ` Ulrich Drepper
2002-09-24 22:02 ` Roland McGrath
2002-09-24 21:55 ` Alexandre Oliva
2002-09-24 22:01 ` Roland McGrath
2002-09-25 10:27 ` Andreas Jaeger
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=or1y7uxa5v.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=aj@suse.de \
--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).