[m-rev.] diff: avoid bogus errors about conflicting modes of operation with mmc --make
Julien Fischer
jfischer at opturion.com
Tue Oct 13 00:37:46 AEDT 2015
Avoid bogus errors about conflicting modes of operation with mmc --make.
compiler/handle_options.m:
Do not set '--compile-only' and '--target-code-only' here if '--make' is
specified as doing so results in bogus errors about conflicting modes
of operation in processes created by 'mmc --make'. '--make' will itself
pass '--target-code-only' to processes it creates when appropriate (i.e.
when target code is actually being generated).
Julien.
diff --git a/compiler/handle_options.m b/compiler/handle_options.m
index e47ec94..48ba237 100644
--- a/compiler/handle_options.m
+++ b/compiler/handle_options.m
@@ -1011,12 +1011,6 @@ convert_options_to_globals(OptionTable0, Target, GC_Method, TagsMethod0,
LibLinkages0 = [_ | _]
),
- % make.m controls generating object code and linking itself,
- % so mercury_compile.m should only generate target code when
- % given a module to process.
- option_implies(make, compile_only, bool(yes), !Globals),
- option_implies(make, target_code_only, bool(yes), !Globals),
-
% This is needed for library installation (the library grades
% are built using `--use-grade-subdirs', and assume that
% the interface files were built using `--use-subdirs').
More information about the reviews
mailing list