Closed GoogleCodeExporter closed 8 years ago
Finally I resolved the issue,
Checking the config.log I realized that libproto uses pthread and test program
does
not try to link against it, so I exported this variable:
"export LDFLAGS=-lpthread"
before executing configure and all went right.
But, where is the problem?, in configure script or in protobuf library?.
Original comment by uesteba...@gmail.com
on 14 May 2009 at 3:19
This is a bug in the configure script. This was recently raised on the protobuf
mailing list: basically pthreads was always required, but until recently you
could
get by, just by chance, without it.
Original comment by cbsm...@gmail.com
on 1 Jun 2009 at 8:44
ok, i've added -lpthread unconditionally to the build... leaving open since
i'm too
lazy to verify that that's the right thing to do... (e.g. on windows)
Original comment by lahike...@gmail.com
on 11 Jun 2009 at 1:02
I saw the same problem on Leopard (10.5.8) and I had to add the lib directory
path when compiling for 64-bit
with the libraries in a non standard location.
Original comment by mfisch...@gmail.com
on 29 Sep 2009 at 8:38
i think you are supposed to add -pthread to CFLAGS if using gcc.
-pthread
Adds support for multithreading with the pthreads library. This option
sets flags for both the preprocessor and linker.
Original comment by robert.e...@gmail.com
on 11 Nov 2009 at 5:45
fixed a long time ago
Original comment by lahike...@gmail.com
on 18 Mar 2010 at 2:25
[deleted comment]
[deleted comment]
execute ./configure LDFLAGS=-lpthread
ERROR:
protobuf test program failed to link:
perhaps you need to add -Llibdir to your LDFLAGS.
why?
Original comment by bcj1...@163.com
on 8 Aug 2010 at 3:29
Original issue reported on code.google.com by
uesteba...@gmail.com
on 14 May 2009 at 12:01