Re-add -nostdlib option and make it actually do something #6824
Conversation
This file contains 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.
In #6778, I removed the
-nostdliboption because it did not have any effect anymore after the cmi cache was removed.However, when building the standard library from scratch, it is actually very helpful to have a command line option that ensures that we do not inadvertently use pre-existing cmi files from the
lib/ocamldirectory. This is especially true for our work in integrating Core into the compiler repo and building all libs with rewatch.I have therefore re-added the option and am now taking it into account in the initialization of
Config.load_pathso that thelib/ocamldirectory is omitted from the load path if the option is set.