Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Confusion over boost::python installation instructions - no bjam

Open
#369 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, python

Research direction

Compare the Boost.Python 1.76.0 no-install quickstart with the Unix installation guide and the Boost.Build documentation linked in the report. Verify whether the instructions should use bjam or b2, then update the installation guidance so a user can follow one consistent build path.

Written by the indexing model from the issue text.

Description

Hi. I'm trying to install boost::python, following the installation instructions given here for boost 1.76.0 (https://www.boost.org/doc/libs/1_76_0/libs/python/doc/html/building/no_install_quickstart.html).

It references Section 5 of the initial install documentation here (https://www.boost.org/doc/libs/1_76_0/more/getting_started/unix-variants.html), asking you to use that to install bjam, then to use bjam to bootstrap the boost:python build. The problem is that, following the instructions as given in Section 5, then attempting to use bjam results in my terminal telling me bjam isn't installed. Furthermore, reading the documentation for version 1.76.0 here (https://www.boost.org/doc/libs/1_76_0/tools/build/doc/html/index.html#bbv2.faq.projectroot) seems to imply bjam no longer exists in boost, and has been supplanted by the b2 installer referenced in the earlier install. Am I missing something to get boost.python working?

Apologies if I'm missing something simple.

Rogan

Dominant language
C++
Stars
537
Forks
223
Avg merge
11h 22m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from boostorg/python

All issues in boostorg/python

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.