When building with the local static OSSP uuid (standalone/macosx):

checking uuid.h usability... no
checking uuid.h presence... yes
configure: WARNING: uuid.h: present but cannot be compiled
configure: WARNING: uuid.h:     check for missing prerequisite headers?
configure: WARNING: uuid.h: see the Autoconf documentation
configure: WARNING: uuid.h:     section "Present But Cannot Be Compiled"
configure: WARNING: uuid.h: proceeding with the preprocessor's result
configure: WARNING: uuid.h: in the future, the compiler will take  
precedence
configure: WARNING:     ## --------------------------------- ##
configure: WARNING:     ## Report this to rpm-devel@rpm5.org ##
configure: WARNING:     ## --------------------------------- ##
checking for uuid.h... yes
checking for uuid_import in -lossp-uuid... no
checking for uuid_import in -luuid... yes

This unusability is due to the conflict with the system headers:

../3rd/bin/ix86-macosx10.4/uuid-1.6.0/uuid.h:94: error: conflicting  
types for 'uuid_t'
/usr/include/unistd.h:121: error: previous declaration of 'uuid_t'  
was here


It occurs when system headers have already been included before,
such as when running the default "confdefs" from configure:

| #ifdef HAVE_UNISTD_H
| # include <unistd.h>
| #endif
| #include <uuid.h>

This should probably be taken care of upstream (in OSSP uuid),
just thought I'd mention it here since RPM5 is affected by it.

--anders