Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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
Developer Community or GitHub 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.
LLVM was bumped (and the build green) on 126.96.36.199.
Can you try again with the most recent version ?
Also whenever LLVM fails can you try the same build options *without* LLVM ? that will make it clear if the issue is related to the linker or the AOT compiler options.
Note that for #1 you need at least 188.8.131.52 to get around the issue (147 is between the mono bump and the related monotouch changes).
Retested with 184.108.40.206.pkg
monotouch_test llvmthumbsgen build successfully without throwing MT3001 error.
Test Configuration and results:
Enabled llvm,thumb,sgen and checked with all linker options (Dont Link, LinkAll, Link SDK). Project built successfully
Disabled LLVM and checked with all linker options. Again Project built successfully
Retested comment #1 with 220.127.116.11.pkg
Disabled llvm and enabled LinkAll assemblies. MT3001 error was thrown.
Build output: https://gist.github.com/GouriKumari/217100fcab091925bb11
As mentioned in comment 2, MT3001 error got fixed in builds newer to 18.104.22.168.pkg.
that's all right? if not please re-open and state what's still failing
Today we have checked this issue with following builds:
X.S 4.0.9(build 15)
And we have checked build the application after changing the options which are mentioned in Comment#3 we are successfully able to build the application, no error appears.
Changing the status to Verified.