List Arkiverade meddelande #16

Från: "Lewis G Rosenthal" <> Meddelandehuvud
Oavkodat meddelande
Ämne: Re: [GNU Ports] Building privoxy - need to specify PTHREAD_LIB - why?
Datum: Tue, 1 Feb 2022 08:24:44 -0500
Till: GNU Ports for eCS Mailing List <>

Hi, Dave...

On 02/01/22 12:52 am, Dave Yeo wrote:
On 01/31/22 09:12 PM, Steven Levine wrote:
In <>, on 02/01/22
   at 03:07 PM, "Paul Smedley" <> said:

Hi guys,

Im assuming that on some platforms, adding -pthreads to the gcc command
line causes -lpthreads to be added by gcc automatically.
See: It would appear that even though our built-in specs understand pthread, we
don't understand it quite as fully as gcc on other platforms.

I see some configure scripts doing 3 or 4 pthread checks before deciding on the one to use for us.
BTW, doesn't privoxy have native OS/2 threads support or was it removed?

Hmmm... Using the configure option:


configure gives me the following ominous message:

checking pthread.h presence... yes
checking for pthread.h... yes
configure: WARNING: pthreads seem to be available but you are using --disable-pthread.
configure: WARNING: This is almost always a mistake and can render Privoxy unacceptable slow.
configure: WARNING: Also various Privoxy features only work when using threads and won't even compile
 without them.

Compiling, I get (as a start):

gcc.exe -c -pipe -g -O2 -Zexe -DNDEBUG    -Wall  cgisimple.c -o cgisimple.o
cgisimple.c: In function 'cgi_show_client_tags':
cgisimple.c:376:10: warning: implicit declaration of function 'privoxy_mutex_lock' \
  376 |          privoxy_mutex_lock(&client_tags_mutex);

I'm not sure what else might need to be done to use native threads vs POSIX. I'll re-read configure as time permits.

Thanks for the suggestion.

PS - I'll bet this just builds fine with EMX. LOL

Lewis G Rosenthal, CNA, CLP, CLE, CWTS, EA
Rosenthal & Rosenthal, LLC      
visit my IT blog      

Prenumerera: Sändning, Uppsamling, Index.
Stoppa prenumeration
Meddelande till ListMaster