From: Ian Wienand <ianw@gelato.unsw.edu.au>
To: linux-ia64@vger.kernel.org
Subject: Re: new syscall-stub support now in CVS glibc
Date: Fri, 12 Dec 2003 03:17:51 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107119918318845@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107110849625591@msgid-missing>
On Wed, Dec 10, 2003 at 06:00:27PM -0800, David Mosberger wrote:
> The latest CVS tree of glibc now sports official support for the new
> syscall-stubs (which enable EPC-based kernel entry and light-weight
> system call handlers).
If you would rather not build this yourself, I have built a version
with a libunwind enabled gcc Debian users should be able to grab by
putting
deb http://www.gelato.unsw.edu.au/~ianw/libc-nptl ./
in /etc/apt/sources.list
and then type
apt-get update
apt-get upgrade
** Note: you want to do this in a chroot environment **
This is just an unoffical packaged version of glibc cvs with these
changes for people who want to try it, I'm sure Debian propper will
update soon.
-i
next prev parent reply other threads:[~2003-12-12 3:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 2:00 new syscall-stub support now in CVS glibc David Mosberger
2003-12-12 3:17 ` Ian Wienand [this message]
2003-12-12 4:09 ` David Mosberger
2003-12-12 4:48 ` Ian Wienand
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=marc-linux-ia64-107119918318845@msgid-missing \
--to=ianw@gelato.unsw.edu.au \
--cc=linux-ia64@vger.kernel.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