Eef Hartman <E.J.M.Hartman@math.tudelft.nl> wrote:
: No, but you can look at the SlackBuild script for the version IN
: the distribution to see how that one was build.
: For instance, the 10.0 appache source is on CD 4, in the
: source/n/apache
: subdir, and the script itself is called "apache.SlackBuild"

: Note that unlike the configure/make way of building a package,
: this is a pure shell (bash) script, there is no correlation with
: any configure options.

Except that the SlackBuild script can (and often does) call ./configure
with the options chosen for the package

For example, in apache.SlackBuild we see:
../configure \
--prefix=/usr \
--enable-static \
--enable-shared

And here we see why Slackware's OpenSSH does not have PAM support from the
openssh.SlackBuild script:
../configure \
--prefix=/usr \
--sysconfdir=/etc/ssh \
--without-pam \
--with-md5-passwords \
--with-tcp-wrappers \
--with-default-path=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin \
--with-ipv4-default \
--with-privsep-path=/var/empty \
--with-privsep-user=sshd \
$ARCH-slackware-linux