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.
Created attachment 2635 [details]
I'm updating my app to ios6 and i having following problem
building application with ARMv7 is not possible to use the flag LLVM ... (error MT3001)
My system configuration is
Reference to question:
Zoltan, this looks like your area:
/var/folders/_3/x0_zyy9j0r5_gg94nc3r51zm0000gn/T/tmp58b5bb1b.tmp/monotouch.dll.7.s:25651:branch out of range
How can I reproduce this ?
In my case happen all time when it's flagged LLVM and supported architecture ARMV7.
Luigi, do you get the same behavior if you create a new project from a template and enable LLVM for that project?
Created attachment 2660 [details]
Created attachment 2661 [details]
Verbose Output Test Project
I have same problem with test project. I have attached Test project and verbose output. Let me know.
The test project has no source files.
sorry. i have attached right one :-)
Created attachment 2662 [details]
Right Test Project
I can reproduce this now, it happens when sgen is enabled, and linking is turned off. The .s file generated by llvm becomes so huge that it causes a linking problem.
As a workaround, you can set the linker behavior to 'link sdk assemblies only'. This is the default, and without it, the resulting application binary will be huge.
*** This bug has been marked as a duplicate of bug 1102 ***