[467] in Pthreads mailing list archive
Re: shared ELF libpthread for Linux
daemon@ATHENA.MIT.EDU (Christopher Provenzano)
Mon Oct 21 20:58:04 1996
Reply-To: proven@cygnus.com
To: Tristan Savatier <tristan@creative.net>
Cc: pthreads@MIT.EDU
In-Reply-To: Your message of "Mon, 21 Oct 1996 13:16:57 PDT."
<326BDA39.582A9BEF@creative.net>
Date: Mon, 21 Oct 1996 20:39:51 -0400
From: Christopher Provenzano <proven@proven.org>
> Dear Chris,
>
> > Am I correct to assume that the machdep_sys_readv and
> > machdep_sys_writev should be removed from readv.c and writev.c,
> > and that the correct version for those routines is in
> > machdep.c ?
>
> Hum... my asumption does not seem right.
>
> In readv.c, the only function defined is machdep_sys_readv(), and
> it is defined only "ifndef HAVE_SYSCALL_READV".
>
> On the other hand machdep.c seems to be designed for overriding
> the "standard" machdep_sys_readv() defined in readv.c by a custom
> machine-dependent version.
>
> So, I suppose that a workaround is to manually define
> the flags HAVE_SYSCALL_READV and HAVE_SYSCALL_WRITEV,
> even though readv and writev are not really
> system calls, but rather custom-defined in machdep.c.
>
> Am I correct ?
No, the correct solution is to remove machdep_sys_readv() and
machdep_sys_writev() from the machdep.c file. I originally thought that
linux was the only OS to not have real syscalls for readv() and writev()
but I've since discovered that IRIX also doesn't have them. I must have
forgotten to remove the code in machdep.c after writing readv.c and
writev.c. No point in duplicating the same code in multiple machdep.c
files.
CAP
