Date: Thu, 26 Oct 2000 20:44:09 -0500 From: Dan Nelson <dnelson@emsphone.com> To: Flemming Froekjaer <froekjaerf@netscape.net> Cc: freebsd-questions@freebsd.org Subject: Re: What's the deal with _THREAD_SAFE? Message-ID: <20001026204408.A14234@dan.emsphone.com> In-Reply-To: <5236E726.3D526C4F.0F2A144B@netscape.net>; from "Flemming Froekjaer" on Thu Oct 26 20:04:37 GMT 2000 References: <0E205B64.7BDA2B7E.0F2A144B@netscape.net> <20001026164517.A11415@dan.emsphone.com> <34FF0427.420B3885.0F2A144B@netscape.net> <20001026182543.A29079@dan.emsphone.com> <5236E726.3D526C4F.0F2A144B@netscape.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Oct 26), Flemming Froekjaer said: > Sorry, my misspelling. I of course ment <pthread.h>... I know that > there's only the one reference to _THREAD_SAFE in the include > directory, but in lib/libc_r (which holds the code you include with > the -pthread switch) there's references to _THREAD_SAFE in basically > all the uthread_*.c source files. I had a pretty hard time figuring > that out myself. :o) Don't worry about the source of libc_r itself; libc_r/Makefile defines _THREAD_SAFE itself, so when the library is compiled, all the functions get added. You don't need it in your source. > I'm coding against FreeBSD 4.1.1-STABLE #0: Thu Oct 12 17:38:38 PDT 2000 > > Would my using g++ have anything to do with the problem? Hopefully not... It shouldn't matter. What is your gcc commandline, and what error are you getting? -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001026204408.A14234>