[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: multithread CPPFLAGS

From: Matthew Woehlke
Subject: Re: multithread CPPFLAGS
Date: Thu, 21 Aug 2008 11:02:45 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20080723 Fedora/ Thunderbird/ Mnenhy/

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 have to export correct
CFLAGS/LIBS to theses application so that they can compile with
threading enabled.
I agree regarding LIBS, but not regarding CPPFLAGS. If the program only
ever sees one thread, even though the library uses multiple threads behind
its back,
  - it does not need to #include <pthread.h>, and

I agree on this one.

  - 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
completely sure this is safe?

Ah, if the libc uses thread-safe errno and the program doesn't... wouldn't that simply break errno? (i.e. libc would set the thread-safe errno and the program would get back something different, and thus never get the right errno when something goes wrong?) Maybe it would work on some platforms, but I'd be really, *really* nervous about it working in general.

Anonymous: I want the following [software] features:
Rex Dieter: ...and a pony. Can't forget the pony. (Ones with frickin' laser beams a bonus.)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]