Date: Wed, 30 Oct 2002 15:48:58 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Doug Rabson <dfr@nlsystems.com> Cc: Daniel Eischen <eischen@pcnet1.pcnet.com>, current@freebsd.org Subject: Re: [PATCH: libc]Re: gnome on current Message-ID: <3DC06FEA.6CAC2717@mindspring.com> References: <20021030233833.C22480-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Rabson wrote: > > You can't have a library that's sort of threaded and sort of not > > threaded: pick one. > > Yes you can - libX11 is *thread safe* but doesn't create threads. When a > real pthreads implementation is present, libX11 uses its implementation of > mutex, cond etc. to ensure its own safety. If the application doesn't link > to a real pthreads implementation, it uses no-op stubs instead. I'm still not understanding; you say that it's thread-safe, but mutex, cond, etc. are not, in fact, thread-safe. Why aren't the libc_r implementations overriding the do-nothing implementations? The entire point of weak vs. strong symbols is that the first strong symbol wins over any weak symbols. It seems to me that you are saying there is a linker recursion problem that is not being correctly addressed because no one wants to admit there is a problem. I guess my question is: if this is all so wrong, how is it that it doesn't fail on Solaris, which does the same thing? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DC06FEA.6CAC2717>