Open Yzrsah opened 5 years ago
I am having the same problem on windows using user-config.jam
. Did you ever find a solution?
[Solution]
Updating gcc to latest version latest releases gcc9.2
Downgrading python3.7 --> python3.6 python releases
[Issue] Path looking for -
'/Users/trionfo1/.virtualenv/kd_local/lib/python3.7/config-3.7m/libpython3.7.a'
and actual path in the virtualenv was /usr/local/Cellar/python/3.7.1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/config-3.7m-darwin
I got the above error while installing uwsgi with following [Libraries] :
Homebrew
Clang 11
Mac Os catalina
python 3.7
uwsgi 2.0.18
pip3
django2.2
Thank you for your contributions. Main development of B2 has moved to https://github.com/bfgroup/b2 This issue has been automatically marked as "transition" to indicate the potential for needing transition to the new B2 development project.
Hello,
When building Boost on macOS Mojave with Homebrew and LLVM+Clang 7.0.0:
First:
Next, build boost: 1)
./bootstrap.sh --with-toolset=clang --with-python=/usr/local/bin/python3 --with-python-version=3.7
2) Small issue: This will cause the build to fail because you also have to provide "--with-python-root=/usr/local/bin/python3 " otherwise path detection is incorrect. Providing the path to the binary twice might be confusing for the user.So fixing that:
1)
./bootstrap.sh --with-toolset=clang --with-python=/usr/local/bin/python3 --with-python-root=/usr/local/bin/python3 --with-python-version=3.7
Now Python paths will be detected incorrectly. (Build will fail later on):
The detected "include path" path is incorrect, because it is missing the "m in "python3.7m" The correct path is
/usr/local/Cellar/python/3.7.1/Frameworks/Python.framework/Versions/3.7/include/python3.7m
The detected config path of the "library path" is incorrect. The correct config path should be:
/usr/local/Cellar/python/3.7.1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/config-3.7m-darwin
It is using only 'config' and not 'config-3.7m-darwin'Therefore I modify the project-config.jam file to add the paths manually:
However this produces a build error:
Because only a single argument is allowed to be passed via libraries. But manually replacing all incorrectly detected paths requires passing multiple paths.