-
Notifications
You must be signed in to change notification settings - Fork 58
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
Boost 1.67.0 Creates NTFS Junction During Install Process #58
Comments
Thanks for letting me know! |
I think I've come up with at least a temporary solution. It seems as though there are some header files in the
to copy those files into |
According to René Rivera, "Those links are supposed to appear only for the git checkout of @Boost_Libraries and are created on demand when headers are reference during the header scanning. Creating those for a release is a bug in the release process." |
PS. It's also a bug in 7-zip that it can't deal with junctions ;-) |
I'm not actually sure if 7-Zip is at fault, given that my build script deletes the source directory before attempting to zip the destination directory. (I didn't investigate whether reversing the order changed anything.) |
Steven Watanabe said: "I think this will fix it, but I haven't tested it: boostorg/release-tools#12" |
Fixed by boostorg/chrono@2b1ddde , verified with Boost 1.69.0. |
You may already be aware of this, but in case you're not, Boost 1.67.0 creates an NTFS junction when compiling and installing. Specifically, it seems to happen with Boost.Chrono:
It's not too severe of an issue (i.e., it doesn't cause the
b2
process to fail), but it will cause 7-Zip to exit with a warning with how your script is currently set up, which in turn causes the script to exit prematurely:There's not much information about this at the moment, aside from this bug report (I'm not the OP, but the other comment is from me). I don't yet know why this is happening with the latest version of Boost, but not the previous version(s).
The text was updated successfully, but these errors were encountered: