Mysterious boost build error #308
Comments
|
Seems to be reproducible, I just hit it again -- so far it's 2 for 2 |
|
3 for 3 |
|
The archive seems to extract correctly, here's the output from a verbose build: STATUS: Installing boost... |
|
I added some extra debug info: STATUS: Installing boost... Looks like maybe a bad archive? If archives from SourceForge are such a problem, how about getting it from a different location? |
|
Actually... the archive seems fine. |
|
Hey Jeremy, we've hit this problem here too -- try building to a location outside of your source tree... |
|
Thanks! I unblocked myself by manually extracting boost to the expected directory. The build is running now, so I'm going to let it keep going and see how it goes. |
|
Bet you could solve the issue by logging off and on again. "The process cannot access the file because it is being used by another process" ---- something terminated and managed to not release file handles. |
|
Hmm, but I was able to delete the files manually and repro again... |
|
We've hit this in some cases in our local testing even after deleting the directory and rebooting, and I'm not sure what's going on yet. This only seems to happen if you build to a location inside the USD source tree; if you build somewhere outside the tree the problem seems to go away. |
|
Filed as internal issue #152499. |
|
This seems to be fixed in v0.8.2 -- at least my first build successfully made it past Boost. |
|
I ran into this again last night and did some more digging. I think the real problem here is that we're running into a 260 character path limit on NTFS. In @jcowles' earlier post, the path to that .html file beneath the boost root directory is 207 characters long! So, if the build script is extracting to some path that is >= 53 characters long it will fail and because of a bug in the build script we'll get that "cannot access file" error instead of seeing the real error from the extraction. A bug report for this was filed with boost here: https://svn.boost.org/trac10/ticket/11677 but the last activity was 2 years ago. Since the problematic file is in a component that we don't use, one possible fix might be to exclude it from the extraction. |
|
Yikes, I run into this problem a lot when dealing with auto-generated files for protobuf language bindings on Windows. I work around it by mapping the root of my tree to a drive letter to shorten the paths. |
…ationStudios#308) When we use MaterialX heighttonormal node to convert a height map to normal map, Storm reports a shader error. error C7522: OpenGL requires constants to be initialized The root cause is that the filter kernels are uninitialized const float c_box_filter_weights[84]; const float c_gaussian_filter_weights[84]; Also logged as USD github issue PixarAnimationStudios#2281
Description of Issue
After running a clean v0.8.1 build, it failed on boost with the following error:
ERROR: [Error 32] The process cannot access the file because it is being used by another process: 'boost_1_61_0.tar.gz'
The directory was empty and the system was left idle while building.
Steps to Reproduce
python build_scripts\build_usd.py --build-monolithic --no-tests --no-docs --no-python --no-imaging --no-ptex --no-embree --alembic --no-hdf5 build_monolithic
System Information (OS, Hardware)
Windows
Package Versions
Build Flags
python build_scripts\build_usd.py --build-monolithic --no-tests --no-docs --no-python --no-imaging --no-ptex --no-embree --alembic --no-hdf5 build_monolithic
Building with settings:
USD source directory C:\src\usd\USD-v0.8
USD install directory C:\src\usd\USD-v0.8\build_monolithic
3rd-party source directory C:\src\usd\USD-v0.8\build_monolithic\src
3rd-party install directory C:\src\usd\USD-v0.8\build_monolithic
Build directory C:\src\usd\USD-v0.8\build_monolithic\build
Building Monolithic shared library
Imaging Off
Ptex support: Off
UsdImaging Off
Python support Off
Documentation Off
Tests Off
Alembic Plugin On
HDF5 support: Off
Maya Plugin Off
Katana Plugin Off
Houdini Plugin Off
STATUS: Installing zlib...
STATUS: Installing boost...
ERROR: [Error 32] The process cannot access the file because it is being used by another process: 'boost_1_61_0.tar.gz'
The text was updated successfully, but these errors were encountered: