Hello,
* Matthew Woehlke wrote on Mon, Aug 25, 2008 at 07:40:07PM CEST:
Bruno Haible wrote:
Yoann Vandoorselaere wrote:
- it does not need to see a thread-aware errno,
hence it does not need to compile with THREADCPPFLAGS.
Not using a thread-aware errno from an application that indirectly
Le jeudi 21 août 2008 à 11:02 -0500, Matthew Woehlke a écrit :
Yoann Vandoorselaere wrote:
Le jeudi 21 août 2008 à 12:28 +0200, Bruno Haible a écrit :
Yoann Vandoorselaere wrote:
Most program using the library currently don't (and probably won't)
depend on GnuLib. They are not multithread
Hi Bruno,
Le lundi 25 août 2008 à 11:46 +0200, Bruno Haible a écrit :
Yoann Vandoorselaere wrote:
- it does not need to see a thread-aware errno,
hence it does not need to compile with THREADCPPFLAGS.
Not using a thread-aware errno from an application that indirectly use
thread
Bruno Haible wrote:
Yoann Vandoorselaere wrote:
- it does not need to see a thread-aware errno,
hence it does not need to compile with THREADCPPFLAGS.
Not using a thread-aware errno from an application that indirectly use
thread through a library (which use thread-aware errno). Are you
Yoann Vandoorselaere wrote:
Most program using the library currently don't (and probably won't)
depend on GnuLib. They are not multithread programs, and in order to
enable the library threaded features, we have to export correct
CFLAGS/LIBS to theses application so that they can compile with
Le jeudi 21 août 2008 à 12:28 +0200, Bruno Haible a écrit :
Yoann Vandoorselaere wrote:
Most program using the library currently don't (and probably won't)
depend on GnuLib. They are not multithread programs, and in order to
enable the library threaded features, we have to export correct
Yoann Vandoorselaere wrote:
Le jeudi 21 août 2008 à 12:28 +0200, Bruno Haible a écrit :
Yoann Vandoorselaere wrote:
Most program using the library currently don't (and probably won't)
depend on GnuLib. They are not multithread programs, and in order to
enable the library threaded features, we
