* Dan Nelson <[EMAIL PROTECTED]> [010124 10:32] wrote:
> In the last episode (Jan 24), Daniel Eischen said:
> > On Wed, 24 Jan 2001, Alfred Perlstein wrote:
> > > * Daniel M. Eischen <[EMAIL PROTECTED]> [010124 05:26] wrote:
> > > > As discussed a few days ago, I've just committed the changes to libc
> > > > and libc_r to allow them to be linked together via -lc_r. If you're
> > > > running -current and have any threaded apps built using libc_r.so.5,
> > > > you'll need to rebuild them without the -pthread option using -lc_r.
> > > >
> > > > For porters, the __FreeBSD_version has been bumped to 500016 to
> > > > reflect the above change.
> > >
> > > This is ambiguous, can you provide old/new examples of how to
> > > compile/link a single C source file?
> >
> > What's not clear ;-) Use -lc_r instead of -pthread.
> >
> > gcc -Wall -o foo foo.c -lc_r
> >
> > The old way was:
> >
> > gcc -Wall -D_THREAD_SAFE -o foo foo.c -pthread
>
> I thought the old way was just -pthread, and it would handle
> everything. I did a quick scan of the devel/ and net/ branches of our
> ports tree, and of 43 thread-using ports, 36 of the ports simply add
> -pthread. Only 7 also add -D_THREAD_SAFE.
>
> The only usage of _THREAD_SAFE in /usr/include is redefinition of
> feof, ferror, clearerr, and fileno to *_unlocked.
-D_THREAD_SAFE used to (or still does) make various foo_r function
prototypes available.
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a jar on my desk."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
