boost - obsolete option

[ken@…]

We build boost using --with-python=python3.

But at the end of the comand explanations we have an option "--with-python=python3: Add this switch to the bootstrap command, if you want Boost to use Python3 instead of Python2. Using Python3 is known to cause the installation to fail on some systems."

That is obviously left over from the past. I suggest we can just drop that option text (I cannot see why anyone would want to use python2 for current boost, and I have no idea if python2 would still be valid for boost).

[Bruce Dubbs]

I removed that option and rebuilt boost. In the log I now have:

[1] gcc-12
[2] gcc-12/release/python-2.7/threadapi-pthread/threading-multi/visibility-hidden
[3] gcc-12/release/build-no/python-2.7/threadapi-pthread/threading-multi/visibility-hidden
[4] gcc-12/release/link-static/python-2.7/threadapi-pthread/threading-multi/visibility-hidden
...
gcc.compile.c++ bin.v2/libs/python/build/gcc-12/release/python-2.7/threading-multi/visibility-hidden/converter/from_python.o
gcc.compile.c++ bin.v2/libs/program_options/build/gcc-12/release/threading-multi/visibility-hidden/cmdline.o
gcc.compile.c++ bin.v2/libs/python/build/gcc-12/release/python-2.7/threading-multi/visibility-hidden/converter/registry.o
gcc.compile.c++ bin.v2/libs/program_options/build/gcc-12/release/threading-multi/visibility-hidden/parsers.o
gcc.compile.c++ bin.v2/libs/python/build/gcc-12/release/python-2.7/threading-multi/visibility-hidden/converter/type_id.o
gcc.compile.c++ bin.v2/libs/python/build/gcc-12/release/python-2.7/threading-multi/visibility-hidden/object/life_support.o

I don't think that's what we want.

Closing.

[ken@…]

Replying to Bruce Dubbs:

I removed that option and rebuilt boost. In the log I now have:

[1] gcc-12
[2] gcc-12/release/python-2.7/threadapi-pthread/threading-multi/visibility-hidden
[3] gcc-12/release/build-no/python-2.7/threadapi-pthread/threading-multi/visibility-hidden
[4] gcc-12/release/link-static/python-2.7/threadapi-pthread/threading-multi/visibility-hidden
...
gcc.compile.c++ bin.v2/libs/python/build/gcc-12/release/python-2.7/threading-multi/visibility-hidden/converter/from_python.o
gcc.compile.c++ bin.v2/libs/program_options/build/gcc-12/release/threading-multi/visibility-hidden/cmdline.o
gcc.compile.c++ bin.v2/libs/python/build/gcc-12/release/python-2.7/threading-multi/visibility-hidden/converter/registry.o
gcc.compile.c++ bin.v2/libs/program_options/build/gcc-12/release/threading-multi/visibility-hidden/parsers.o
gcc.compile.c++ bin.v2/libs/python/build/gcc-12/release/python-2.7/threading-multi/visibility-hidden/converter/type_id.o
gcc.compile.c++ bin.v2/libs/python/build/gcc-12/release/python-2.7/threading-multi/visibility-hidden/object/life_support.o

I don't think that's what we want.

Closing.

Bruce, I was not intending to suggest that the *switch* in our current configure should be removed. I suppose that boost prefers to look for 'python' and is apparently still happy to use python2.

BUT: the explanation for the switch still marks it up as an option instead of a command, and says "Using Python3 is known to cause the installation to fail on some systems."

Do we really want to imply that python3 is not good enough on some current LFS systems ? ^_

[ken@…]

Ah, I see you have already fixed that part.