Date: Fri, 08 Feb 2002 08:37:11 -0600 From: Stephen Montgomery-Smith <stephen@math.missouri.edu> To: "M. Warner Losh" <imp@village.org> Cc: sobomax@FreeBSD.ORG, jdp@FreeBSD.ORG, deischen@FreeBSD.ORG, jasone@FreeBSD.ORG, hackers@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: Linking libc before libc_r into application causesweirdproblems Message-ID: <3C63E297.F90D5E82@math.missouri.edu> References: <1013147180.73417.2.camel@notebook> <20020207.234939.69060047.imp@village.org> <3C63773A.8DBF36F6@math.missouri.edu> <20020208.003223.29577858.imp@village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"M. Warner Losh" wrote: > > In message: <3C63773A.8DBF36F6@math.missouri.edu> > Stephen Montgomery-Smith <stephen@math.missouri.edu> writes: > : cc -o test test.c -pthread -D_THREAD_SAFE > : > : or am I misunderstanding something? > > Ah, yes. -D_THREAD_SAFE is technically needed. > I am curious - what are the possible consequences if you forget to include -D_THREAD_SAFE? I have done many compilations having forgotten to include this flag, with no obvious problems. Did I just get lucky? -- Stephen Montgomery-Smith stephen@math.missouri.edu http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C63E297.F90D5E82>