Opened 18 years ago

Closed 18 years ago

Last modified 8 years ago

#1026 closed defect (invalid)

Postfix requires threads library to build.

Reported by: stef@… Owned by: blfs-book@…
Priority: high Milestone:
Component: BOOK Version: SVN
Severity: blocker Keywords:
Cc:

Description

gcc -Wmissing-prototypes -Wformat -DHAS_PCRE -g -O -I. -I../../include -DLINUX2 -o master master.o master_conf.o master_ent.o master_sig.o master_avail.o master_spawn.o master_service.o master_status.o master_listen.o master_vars.o master_wakeup.o master_flow.o ../../lib/libglobal.a ../../lib/libutil.a -L/usr/lib -lpcre -ldb -lnsl -lresolv /usr/lib/libdb.so: undefined reference to `pthread_condattr_setpshared' /usr/lib/libdb.so: undefined reference to `pthread_mutexattr_destroy' /usr/lib/libdb.so: undefined reference to `pthread_mutexattr_setpshared' /usr/lib/libdb.so: undefined reference to `pthread_mutexattr_init' /usr/lib/libdb.so: undefined reference to `pthread_mutex_trylock' collect2: ld returned 1 exit status make: * [master] Error 1 make: * [update] Error 1

I'm guessing it's the NPTL in Berkeley makes postfix upset.

To build successfully

AUXLIBS="$AUXLIBS -lpthread"

Change History (7)

comment:1 by igor@…, 18 years ago

I've built it successfully without AUXLIBS="$AUXLIBS -lpthread".

comment:2 by stef@…, 18 years ago

hmm...

I'm running LFS v6 Test release.

Are you building against LFS 5.1?

Maybe a linuxthreads vs NPTL thing?

comment:3 by igor@…, 18 years ago

I'm running LFS 6.0-testing-20041010 and have Berkeley DB installed by the book. Looks like we need some more confirmations.

comment:4 by thomasp@…, 18 years ago

Are you sure you've built db with -lpthread support. Check you /usr/lib/libdb-4.2.la file and see if you find a reference to -lpthread, if not then db should be recompiled. I believe that the current postfix instructions rely on db being compiled as it is in the book.

As a side note I have no trouble building postfix against db with a LFS 6 based system.

comment:5 by stef@…, 18 years ago

Gah... you're right. My mistake. Apologies, I am a muppet. Just as you say, I didn't have my libdb built right. I've rebuilt both and no longer see the error.

comment:6 by igor@…, 18 years ago

Resolution: invalid
Status: newclosed

comment:7 by bdubbs@…, 8 years ago

Milestone: old

Milestone old deleted

Note: See TracTickets for help on using tickets.