Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compiler intermittently fails to find include files after April 2018 upgrade #3204

Closed
pgerell opened this issue May 16, 2018 · 3 comments
Closed

Comments

@pgerell
Copy link

pgerell commented May 16, 2018

  • Your Windows build number: Microsoft Windows [Version 10.0.17134.48]

  • What you're doing and what's happening: When building my project using parallel jobs (make -j8) the compiler sometimes fails to find include files. If I restart make the file is found and the build continues only to fail at some other file. Eventually the project will build. If using make without the -j-option it always builds at first attempt. The file not found always resides on DrvFs, never on VolFs.

In file included from /home/pg/repos/tools/build/external_boost/boost_x/include/boost/type_traits/alignment_of.hpp:15:0,
                 from /home/pg/repos/tools/build/boost/optional/optional.hpp:36,
                 from /home/pg/repos/tools/build/boost/optional.hpp:15,
                 from /home/pg/repos/tools/src/shared/utils/Report.cpp:5:
/home/pg/repos/tools/build/boost/type_traits/intrinsics.hpp:16:10: fatal error: boost/type_traits/detail/config.hpp: No such file or directory

 #include <boost/type_traits/detail/config.hpp>
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
@therealkenc
Copy link
Collaborator

#2712 #2780 #2484 #2448 #2495 #1735. Your scenario might be addressed in 17655. You are on '134.

@pgerell
Copy link
Author

pgerell commented May 16, 2018

I guess you're right. The description in the Relese Notes for 17655 describes my problem.
I hope an update for this will be available soon as joining the Windows Insider Program is not always an option.

@therealkenc
Copy link
Collaborator

Calling this dupe #2712 because @heldchen confirmed it probably didn't manifest in 16299, which I assume is from whence you came. Bonne chance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants