Bug 56105 - mono-cil-strip should un-set env variables that cause it to fail
Summary: mono-cil-strip should un-set env variables that cause it to fail
Alias: None
Product: Tools
Classification: Mono
Component: other ()
Version: 5.0 (2017-02)
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-05-08 18:21 UTC by Chris Hamons
Modified: 2017-09-01 09:04 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Chris Hamons 2017-05-08 18:21:40 UTC
XM was setting MONO_PATH for all mono tool invocations during our AOT process, which breaks mono-cil-strip if the system mono / XM mono drift too much.

@kumpera suggested that we should unset variables to prevent this breakage (I'm going to fix my invocation as well).
Comment 1 Rodrigo Kumpera 2017-05-08 18:23:44 UTC
I don't see any use-case for setting things like MONO_PATH & friends when using the shell scripts as I'd assume the normal path is to run the assemblies directly.
Comment 2 Marek Safar 2017-09-01 09:04:24 UTC
Please unset the variable outside of the tool itself