From: Randolph Chung <randolph@tausq.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] what's up with the ipc syscalls?
Date: Sun, 2 Nov 2003 10:12:52 -0800 [thread overview]
Message-ID: <20031102181252.GY28967@tausq.org> (raw)
In-Reply-To: <20031102180150.GA14554@solo.franken.de>
> if this makes a difference, something in ipc/util.c is missing. When I
> added the code above, I also made the ipc_parse_version only return
> IPC_64, because we never had IPC_OLD. Older glibc made the call with
> IPC_64 set, so we needed the wrapper in sys_parisc.c. I just looked
> at the 2.4 version of ipc/util.c and it's still ok ...
Ah! that explains it.... that change was not brought forward to 2.6...
i was wondering why my test worked on 2.4 and failed on 2.6....
anyway, if we are only supporting IPC_64, then why mask off the IPC64
bit in the wrapper? if the ipc/utils.c stuff isn't there, wouldn't it
default to doing the right thing when IPC_64 is set?
right now glibc *doesn't* call the syscall with IPC_64, but i'm about to
make it do that again.
thanks,
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2003-11-02 18:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 8:24 [parisc-linux] what's up with the ipc syscalls? Randolph Chung
2003-11-02 18:01 ` Thomas Bogendoerfer
2003-11-02 18:12 ` Randolph Chung [this message]
2003-11-02 21:42 ` Thomas Bogendoerfer
2003-11-02 21:55 ` Randolph Chung
2003-11-03 8:59 ` Thomas Bogendoerfer
2003-11-02 22:56 ` Carlos O'Donell
2003-11-03 8:56 ` Thomas Bogendoerfer
2003-11-03 21:41 ` Carlos O'Donell
2003-11-10 23:44 ` Thomas Bogendoerfer
2003-11-11 20:41 ` Joel Soete
2003-11-11 21:46 ` Carlos O'Donell
2003-11-12 15:32 ` Thomas Bogendoerfer
2003-11-14 0:35 ` Carlos O'Donell
2003-11-12 19:54 ` JSO
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=20031102181252.GY28967@tausq.org \
--to=randolph@tausq.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tsbogend@alpha.franken.de \
/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