> Yes, this is the right list.
Fine.

> If it depends on -I and -L flags, using the buildlink3.mk framework  
> should just DTRT.
Looks like it, at least as far as I can tell (I only learned  
yesterday what buildlink3 is about and don't really know anything  
about GNU autoconfigure).
In config.log, just after the test for LDAP, there is a test for  
ldap_enable_cache that fails. So I get the following log message:

[wrapper.sh] note: The real command line, after the pkgsrc wrapper, was:
/Volumes/User/ef-cliff/local/build/pkgsrc/sysutils/am-utils/work/.gcc/ 
bin/gcc -o conftest -pipe -O2 -DLDAP_DEPRECATED -I/Volumes/User/ef- 
cliff/local/build/pkgsrc/sysutils/am-utils/work/.buildlink/include - 
D_P1003_1B_VISIBLE -no-cpp-precomp -L/Volumes/User/ef-cliff/local/ 
build/pkgsrc/sysutils/am-utils/work/.buildlink/lib conftest.c  -lldap

So it seems that the magic infrastructure is getting it right.

> @VARBASE@/run.  VARBASE defaults to /var, so this will work on most  
> systems.  Those who tune VARBASE should know what they are doing.
I first thought I should use VARBASE, but then I saw other packages  
(cyrus-imapd, for example) using /var.
Perhaps the documentation could clarify this?

> Hope this helps,
Yes, thanks.
How does the rest of my doings look? I guess I must be making some  
mistakes after all.
What's the usual way of getting a package audited and possibly included?