Open
Conversation
Linking programs using mingw on win32 sometimes causes a pipe-nt file to be generated. Tup should ignore this file type as it is a temporary file produced by the linker.
ba903ec to
1306ed4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linking programs using MinGW on Win32 sometimes causes a
pipe-ntfile to be generated. Tup should ignore this file type as it is a temporary file produced by the linker.I can't definitively determine what these files are, as I'm struggling to find anything online. So if anyone has any more info, that would be appreciated! I was compiling using version
13.1.0ofx86_64-w64-mingw32-gcc.I've tried to include as much of the
pipe-ntfile string as possible to avoid a clash with expected file types.I ran into this when trying to create a fresh build of Tup from the
masterbranch: