On Wed, Jul 16, 2008 at 6:30 PM, Johnny Hughes <johnny at centos.org> wrote: > tblader wrote: >> >> Hello All. >> How do I find out what flags were used to compile >> the Centos openldap-2.3.27-8.el5_2.4 rpm package? >> I'm specifically wondering if it was compiled with >> --enable-lmpasswd >> >> Thanks! >> > If you download the SRPM and install it, then you can look at the spec file. > > Server is built like this: > > --enable-plugins \ > --enable-slapd \ > --enable-slurpd \ > --enable-multimaster \ > --enable-bdb \ > --enable-hdb \ > --enable-ldap \ > --enable-ldbm \ > --with-ldbm-api=%{ldbm_backend} \ > --enable-meta \ > --enable-monitor \ > --enable-null \ > --enable-shell \ > --enable-sql=mod \ > --disable-perl \ > --disable-shared \ > --disable-dynamic \ > --enable-static \ > --with-kerberos=k5only > > Client like this: > > --disable-slapd \ > --disable-slurpd \ > --enable-shared \ > --enable-dynamic \ > --enable-static \ > --without-kerberos \ > --with-pic > Slightly OT, but related to this question and answer, I'd like to know what options are used to build the openssh-4.3p2-26.el5 package. Fetching the SRPM and exploring in there I can see the %configure section in the openssh.spec: %configure \ --sysconfdir=%{_sysconfdir}/ssh \ --libexecdir=%{_libexecdir}/openssh \ --datadir=%{_datadir}/openssh \ --with-tcp-wrappers \ --with-rsh=%{_bindir}/rsh \ --with-default-path=/usr/local/bin:/bin:/usr/bin \ --with-superuser-path=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin \ --with-privsep-path=%{_var}/empty/sshd \ --enable-vendor-patchlevel="FC-%{version}-%{release}" \ --disable-strip \ --without-zlib-version-check \ %if %{nss} --with-nss \ %endif %if %{scard} --with-smartcard \ %endif %if %{rescue} --without-pam \ %else --with-pam \ %endif %if %{WITH_SELINUX} --with-selinux \ %endif %if %{WITH_AUDIT} --with-linux-audit \ %endif %if %{kerberos5} --with-kerberos5${krb5_prefix:+=${krb5_prefix}} %else --without-kerberos5 %endif But many of these %if's leave me wondering what was actually used. Is there a way to query the resultant binary files for their options? -- Thanks, -Bob