[PATCH] Correct symbol defined for OpenBSD with -pthread flag

The attached patch corrects the symbol being defined for OpenBSD when using the
-pthread flag so as to use _REENTRANT instead of _POSIX_THREADS to match the
behavior of our system compilers and compilers in the ports tree.

CVSROOT: /cvs
Module name: src
Changes by: kurt@cvs.openbsd.org 2012/04/12 06:09:30

Modified files:
     lib/libpthread/include: pthread.h
     gnu/egcs/gcc/config: openbsd.h
     gnu/egcs/gcc/config/m68k: openbsd.h
     gnu/egcs/gcc/config/m88k: openbsd.h
     gnu/gcc/gcc/config: openbsd.h
     gnu/gcc/gcc/config/m68k: openbsd.h
     gnu/gcc/gcc/config/rs6000: sysv4.h
     gnu/usr.bin/gcc/gcc/config: openbsd.h
     gnu/usr.bin/gcc/gcc/config/m68k: openbsd.h
     gnu/usr.bin/gcc/gcc/config/m88k: openbsd.h
     gnu/usr.sbin/sendmail/cf/cf: Makefile

Log message:
Remove incorrect -pthread preprocessor define _POSIX_THREADS and replace
with _REENTRANT. Also remove undef _POSIX_THREADS in phread.h.
From brad@comstyle.com. okay guenther@

clang_pthread.diff (456 Bytes)

Applied in r155535, thanks!

Applied in r155535, thanks!

I don't follow the LLVM/Clang development process... will this be a
part of the 3.1 release?

Applied in r155535, thanks!

I don't follow the LLVM/Clang development process... will this be a
part of the 3.1 release?

Please send an email to Bill Wendling, asking him to pull these patches in. You can tell him that I approve both of these for 3.1.

Thanks!

-Chris

Just FYI, there was also another soname patch on the LLVM-commits list as you said to send it there.

Thank you for dealing with these patches.

Applied in r155535, thanks!

I don't follow the LLVM/Clang development process... will this be a
part of the 3.1 release?

Please send an email to Bill Wendling, asking him to pull these patches in. You can tell him that I approve both of these for 3.1.

Just FYI, there was also another soname patch on the LLVM-commits list as you said to send it there.

Thanks for the pointer, I missed it.

Thank you for dealing with these patches.

No problem, thanks for the patches! Just send Bill the rev #'s and my approval and he'll take care of merging the 3 patches into the release branch.

-Chris