Bryan Kadzban wrote:
Not with most packages, when they use fairly recent autoconf versions.
The m4 configure.{in,ac} macros to add --enable-X options take a pair of
expressions (shell syntax). One is the default action (it gets run if
neither --enable-X nor --disable-X is passed to configure). The other
is the set of commands to run if one of those args is passed.
These expressions receive an $enableval variable. If --disable-X is
passed, then $enableval is equal to no. If --enable-X=blah is passed,
then $enableval is equal to blah.
Nice. Thanks for the explanation, Bryan. :)
--
Jeremy Huntwork
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
