On 18/1/18 9:30 am, Joel Sherrill wrote: > Why can't we change it to here for 4.10? > > http://www.multiprecision.org/downloads/mpc-0.8.1.tar.gz >
We could however it leaves us open to the same issue that started us looking at this problem and there is a push to make 4.10 a long term supported release. If the home site changes it breaks the release branch. With RPM tool's was the host's (distros) shared library version being used? I seem to remember the view at the time was host's version was preferred cause distro maintainers always know best. If this is the case which version is being used? I see the alternatives as: 1. Investigate the role MPC plays and what effect it has on the generated code. 2. Make MPC a special and hope the web site stays the same. No matter what path we take we need to make sure we are happy with the generated code for the RSB tools to make a release. How do we do this? a. Assume it is OK if the tests results match. b. Check the generated code. Checking the generated code requires a build of the 4.10.2 kernel with the RPM tools. If this path is taken I need a tarball of the installed only 4.10.2 kernel built with RPM tools for selected archs. I can then check the generated code. I have no ability to install and run the RPM tools. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel