On Tue, 2008-01-01 at 04:10 +, Samuel Thibault wrote:
> Thomas Bushnell BSG, le Thu 27 Dec 2007 18:06:39 -0800, a écrit :
> > > Now, that said, we'd have to modify libc's to also include
> > > a provided by the hurd's libpthread.
> >
> > Yes, certainly, or at least a general Hurdish one or
ysdeps/generic/pt-atfork.c 10 Oct 2002 23:05:06 -
1.1
+++ libpthread/sysdeps/generic/pt-atfork.c 1 Jan 2008 04:07:46 -0000
@@ -27,3 +27,5 @@ pthread_atfork (void (*prepare) (void),
{
return ENOSYS;
}
+
+stub_warning (pthread_atfork)
Index: libpthread/sysdeps/generic/pt-getcp
On Fri, 2007-12-28 at 02:04 +, Samuel Thibault wrote:
> Actually, it happens that in the pike7.6 case, it doesn't, because its
> configure.in doesn't use AC_CHECK_FUNCS for that function. Yes, that's
> evil, but that's unfortunately what people do.
So then they get what they deserve. :)
> N
Thomas Bushnell BSG, le Thu 27 Dec 2007 17:25:01 -0800, a écrit :
> > Ah, you mean in I guess? However, that's a GNU extension,
> > which pike7.6 will most probably not want to depend on.
>
> It's using *configure*. That's a GNU thing already. If it's using
> configure, and not wanting to do g
; We are supposed to gave libc #defines that say that a function is a stub
> > > > when it just returns ENOSYS, which configure checks for. Or something
> > > > like that.
> > >
> > > You mean the configure of those programs that try to use
> >
> > > when it just returns ENOSYS, which configure checks for. Or something
> > > like that.
> >
> > You mean the configure of those programs that try to use
> > pthread_atfork()?
>
> Yes. This is how it works for other functions in general.
Ah, you mean
Or something
> > like that.
>
> You mean the configure of those programs that try to use
> pthread_atfork()?
Yes. This is how it works for other functions in general.
ry to use
pthread_atfork()?
Samuel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, 2007-12-22 at 01:35 +, Samuel Thibault wrote:
> Hello,
>
> At least in pike7.6, ./configure detects pthread_atfork() and then the
> resulting program uses it, and fails because for now our implementation
> is
>
> return ENOSYS;
>
> If we weren't pr
Hello,
At least in pike7.6, ./configure detects pthread_atfork() and then the
resulting program uses it, and fails because for now our implementation
is
return ENOSYS;
If we weren't providing the function, pike would manage to work without
it. So until we have a proper implementation may
10 matches
Mail list logo
