On Mon, May 17, 2010 at 10:14:38AM -0000, john_espiro wrote: > > --- In milter-greylist@yahoogroups.com, "Johann E. Klasek" > > Too many "yes" appearing here where a path value is probably expected ... > > > > Instead of /usr/lib "/usr/lib/lib" is taken as ld argument ... > > Similar /usr/lib/include ... some --with... argument to configure should > > take a "/usr" instead of "/usr/lib" ... > > I changed my configure line to what you suggested and I get the following: > > configure:6455: result: no > configure:6460: checking for pthread_create in -lpthreads -lpthread > configure:6495: gcc -o conftest -g -O2 -Wall -Iyes/include -I/usr/include -Iyes/include -DUSE_GEOIP -Lyes/lib -Wl,--rpath=yes/lib -L/usr/lib -Wl,--rpath=/usr/lib -Lyes/lib -Wl,--rpath=yes/lib conftest.c -lpthreads -lpthread -lGeoIP >&5 > /usr/bin/ld: cannot find -lpthreads > collect2: ld returned 1 exit status > configure:6502: $? = 1 I tried it at a similar environment and following can be seen: If you give the configure option "--with-libGeoIP" *without* a real path via an equate, configure asumes a "yes" which is used in every compile config test. This currupts every configure test since on, because "-lGeoIP" is attached but not found. "configure" thinks -pthread is missing but in real libGeoIP is the cause for the failure of this compile test. The autoconf setup and thus configure does not search for the location or verify the existence of a library given by "--with-....". I don't know this could be solved better in autoconf, maybe Manu does. ;) Try a configure without --with-libGeoIP or give a "--with-libGeoIP=/my/path/to/libGeoIP" ... (e.g. --with-libGeoIP=/usr/local, "/lib" or "/include" is added automatically). Johann E. K.
Message
Re: [milter-greylist] Re: Required libpthread not found. Use --with-libpthread
2010-05-17 by Johann E. Klasek
Attachments
- No local attachments were found for this message.