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 through a library (which use thread-aware errno). Are you > > completely sure this is safe? > > Instead of discussing whether I'm "completely sure" and what we can "assume", > can you show a test program that decides the question without any doubt?
We'd need to know the problem deeper in order to write a specific test case (part of which should be written within a shared library). Right now, what has been discussed is a potential problem with errno, but that one is not especially harmful, and depending on the system, there might be other issues. Note that I wrote a simple test case using libprelude, and checking errno value from a program using the threaded libprelude features, but not using any specific threads CFLAGS in order to compile: no problem noticed. Is there any specific reason why you oppose adding this THREADCPPFLAGS variable? It's a two line change and can always be useful (example: providing thread dependencies to other program that might want to use thread). -- Yoann Vandoorselaere <[EMAIL PROTECTED]>
