[Top][All Lists]

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

Re: multithread CPPFLAGS

From: Yoann Vandoorselaere
Subject: Re: multithread CPPFLAGS
Date: Thu, 21 Aug 2008 10:55:19 +0200

Le jeudi 21 août 2008 à 00:54 +0200, Bruno Haible a écrit :
> Yoann Vandoorselaere wrote:
> > - Isolate thread specific CPP flags into THREADCPPFLAGS (this is useful
> > for a library to propagate threads specific CPPFLAGS).
> What do you mean by that? Do you mean that the users of a library need to
> use the same CPPFLAGS as those with which library was compiled? This would
> not be right in the majority of cases, IMO.
> Let's look at the two cases:
>   - OSF/1: need to modify CPPFLAGS so that cc groks <pthread.h>.
>     If your library's header files make use of <pthread.h> then the user
>     of your library will require the same CPPFLAGS, otherwise not.
>     In the first case the program that uses the library should use
>     threadlib.m4 too.
>   - AIX, FreeBSD, Solaris: need to modify CPPFLAGS in order to disable
>     the single-thread-optimized 'errno'. If the program that uses your library
>     uses multiple threads, it needs to modify CPPFLAGS. If it is a single-
>     threaded program, it does not need it.
> What's the case you have in mind?

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.

Yoann Vandoorselaere <address@hidden>

reply via email to

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