'configure' does not recognise '--without-python'
During Boost build, a line pops up saying "to avoid seeing this message again, use option --without-python". However, if you specify this as a "./configure" option, configure halts saying --without-python is unrecognised. I can live without it/work around it, but it should presumably be fixed ... Regards, Mike
MikeW
During Boost build, a line pops up saying "to avoid seeing this message again, use option --without-python".
However, if you specify this as a "./configure" option, configure halts saying --without-python is unrecognised.
I can live without it/work around it, but it should presumably be fixed ...
Which version of Boost, Boost.Build, etc. are you using? -- Dave Abrahams Boost Consulting www.boost-consulting.com
David Abrahams
MikeW
writes: During Boost build, a line pops up saying "to avoid seeing this message again, use option --without-python".
However, if you specify this as a "./configure" option, configure halts saying --without-python is unrecognised.
I can live without it/work around it, but it should presumably be fixed ...
Which version of Boost, Boost.Build, etc. are you using?
Downloaded file was boost_1_33_1.tar.gz, no separate Boost.build version. (Workaround - once I had 'configure'd, I edited the generated Makefile to say BJAM_CONFIG=--without-python ... is that also an env var ?) Thanks, Mike
David Abrahams
MikeW
writes: During Boost build, a line pops up saying "to avoid seeing this message again, use option --without-python".
However, if you specify this as a "./configure" option, configure halts saying --without-python is unrecognised.
I can live without it/work around it, but it should presumably be fixed ...
Which version of Boost, Boost.Build, etc. are you using?
(version boost_1_33_1) It would be nice for 'configure' to allow a bit of control over which library variants were built as well. Currently, 24 variants are built for each library specified, with no --option to cut this down to a more sensible level. Mike
MikeW
During Boost build, a line pops up saying "to avoid seeing this message again, use option --without-python".
However, if you specify this as a "./configure" option, configure halts saying --without-python is unrecognised.
I can live without it/work around it, but it should presumably be fixed ...
Regards, Mike
I think you can get this setting by saying --without-libraries=python - just from a reading of the configure file. Mike
participants (2)
-
David Abrahams -
MikeW