From: Jack Howarth <howarth@fuse.net>
To: geoffk@cygnus.com, Franz.Sirl-kernel@lauterbach.com,
drepper@cygnus.com, libc-alpha@sources.redhat.com,
linuxppc-dev@lists.linuxppc.org
Subject: Re: [RFC] IPC64 with glibc-2.2 and linux-2.4
Date: Mon, 25 Sep 2000 22:38:58 -0400 [thread overview]
Message-ID: <39D00C41.82E2B00D@fuse.net> (raw)
Geoff,
I believe I have covered all of the combination of tests you asked
about concerning
Franz's glibc 2.1.94 and Linux 2.4-test9 patches for the IPC64 issue.
Again this problem
arose when we recompiled XFree86 4.0.1 against glibc 2.1.9x. Thus I have
done the following
tests...
1) XFree86 built against patched glibc 2.1.94 with patched Linux
2.4-test9 - gnome is working now
2) XFree86 built against glibc 2.1.3 with patched Linux 2.4-test9 -
gnome is working....always did before
3) XFree86 built against patched glibc 2.1.94 with Linux 2.2.17pre20 -
gnome is working now
4) XFree86 built against glibc 2.1.3 with Linux 2.2.17pre20 - gnome is
working
I believe we are safe with Franz's proposed patch and the only question
is do we increase the seq
field to 32 bits from 16 bits.
Jack
ps Of course without Franz's patches to glibc 2.1.94 and Linux
2.4-test9, tests 1 and 3 would have
failed when I tried to run gnome.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-09-26 2:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-26 2:38 Jack Howarth [this message]
[not found] <Franz Sirl's message of "Mon, 25 Sep 2000 11:10:45 +0200">
[not found] ` <Franz Sirl's message of "Sun, 24 Sep 2000 21:50:44 +0200">
2000-09-24 19:50 ` [RFC] IPC64 with glibc-2.2 and linux-2.4 Franz Sirl
2000-09-25 6:51 ` Ulrich Drepper
2000-09-25 9:10 ` Franz Sirl
2000-09-25 15:25 ` Ulrich Drepper
2000-09-25 15:54 ` Franz Sirl
2000-09-25 16:08 ` Ulrich Drepper
2000-09-25 21:24 ` Geoff Keating
2000-09-26 21:24 ` Franz Sirl
2000-09-27 0:45 ` Geoff Keating
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=39D00C41.82E2B00D@fuse.net \
--to=howarth@fuse.net \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=drepper@cygnus.com \
--cc=geoffk@cygnus.com \
--cc=libc-alpha@sources.redhat.com \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.