Is there a way to find out what "./configure" options on a given
software package (say, for example, apache) would produce the package
as it is by default in Slackware (10.0, to be specific)? That is, the
options that were used when the package was built into the distro?


-David

47computers@gmail.com wrote:
> Is there a way to find out what "./configure" options on a given
> software package (say, for example, apache) would produce the package
> as it is by default in Slackware (10.0, to be specific)? That is, the
> options that were used when the package was built into the distro?

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.
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************

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

47computers wrote:

> Is there a way to find out what "./configure" options on a given software
> package (say, for example, apache) would produce the package as it is by
> default in Slackware (10.0, to be specific)? That is, the options that
> were used when the package was built into the distro?

See:
ftp://ftp.bit.nl/mirror/slackware/sl...che.SlackBuild

--
Wim

On Fri, 24 Mar 2006 22:03:35 +0000, Melissa Danforth wrote:

> Eef Hartman <E.J.M.Hartman@math.tudelft.nl> wrote:
> : No, but you can look at the SlackBuild script for the version IN
<snip>
/
> 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 \
<snip>
>
Yes, this is one place /* where */ the PAM option is off. It does not
get into the reason /* why */ it is off ;-) Also, adding PAM would
require more than just toggling this switch.

--
Douglas Mayne