Bug 1255204
| Summary: | support xbuild targeting .net framework 2.0 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hin-Tak Leung <htl10> |
| Component: | mono | Assignee: | Xavier Lamien <lxtnow> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 27 | CC: | chkr, claudiorodrigo, itamar, lxtnow, paul, pokorra.mailinglists |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-30 18:35:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Hin-Tak Leung
2015-08-20 00:31:07 UTC
The problem is, that the tarball of Mono 4.x contains the 2.0 dlls precompiled. So according to the Fedora rules, we have to delete them and cannot use them in the package. One option for you could be to use the Xamarin RPMS, according to http://www.mono-project.com/docs/getting-started/install/linux/#centos-fedora-and-derivatives Those packages include the 2.0 and 4.0 dlls. The even better option that I recommend (and you mentioned already): It is quite easy to upgrade your project to support the 4.5 framework. We have done this for all packages in Fedora that depend on Mono quite similar to this: sed -i "s#gmcs#mcs#g" configure sed -i "s#gmcs#mcs#g" configure.in find . -name "*.sln" -print -exec sed -i 's/Format Version 10.00/Format Version 11.00/g' {} \; find . -name "*.csproj" -print -exec sed -i 's#ToolsVersion="3.5"#ToolsVersion="4.0"#g; s#<TargetFrameworkVersion>.*</TargetFrameworkVersion>##g; s#<PropertyGroup>#<PropertyGroup><TargetFrameworkVersion>v4.5</TargetFrameworkVersion>#g' {} \; Thanks for the explanation. I'll see if I can just drop the precompiled dlls into /usr/lib/mono/2.0 and have them working. As I wrote earlier, as a developer one might like to develop for an older runtime stll in use - i.e. similiar to using compat-gcc-34-c++ and compat-gcc-34-g77 instead of gcc/gfortran, to support users who are not upgrading. At the moment I have a slightly different and unusual need compared to this general one: I need to use a binary-only library that works well under MS .Net 2 in wine, but not in mono (either native or under wine). This is a mono bug/deficiency, but first I need to be able to do apple-to-apple build of a small test wrapper to file the issue :-). I found that I can simply drop the binaries from git://github.com/mono/reference-assemblies.git into /usr/lib/mono/{2.0,3.5,4.0} and xbuild then seem to be able to target the older frameworks and build for them. It seems to run the compiler
with the /nostdlib option then explicitly referencing the versioned libraries,
which is somewhat expected.
However, "mono --runtime=v2.0.50727 ..." still won't work, and comparing those
directories with win32 mono's under wine, I found a whole lot of *.exe missing.
That probably explains it.
I'll leave the bug open, in case there is a way of making it work under redhat's
"not shipping 3rd party binaries" policy in the future.
Actually, since older mono supports the older runtime, the sources of the older runtime - or a compatible version of it - must have shipped with older mono. So one way of not using the reference binaries is to scavenge the older source from older mono. It might be quite painful to make older sources build with newer compiler, though. :-(. This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Still a problem with f25 If we were including Mono 3.x from source in the Fedora packages, how would we provide security updates for that? Xamarin does not support Mono 3.x anymore, I think. I honestly don't think your issue will be resolved with Fedora packages. My suggestion stands to use the Xamarin packages instead. Would that work for you? mono 4.4 moves the reference assemblies to a slightly different place (adding '-api' to the directory name). ATM I unpack the src rpm and drop the fedora patch, and rebuild... but I reckon building for older runtime/older windows isn't that rare a need. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. still a problem in fc27 This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |