[PATCH] gcc: Reference GNU's FTP site for all GCC parts.

Joel Sherrill joel at rtems.org
Wed Jan 17 22:30:17 UTC 2018


Why can't we change it to here for 4.10?

http://www.multiprecision.org/downloads/mpc-0.8.1.tar.gz

--joel

On Tue, Jan 16, 2018 at 8:51 PM, Chris Johns <chrisj at rtems.org> wrote:

> On 17/1/18 1:04 pm, Joel Sherrill wrote:
> > On Jan 16, 2018 6:50 PM, "Chris Johns" <chrisj at rtems.org
> > <mailto:chrisj at rtems.org>> wrote:
> >
> >     On 17/1/18 9:19 am, Chris Johns wrote:
> >     > -%source set mpc
> >     http://www.multiprecision.org/mpc/download/mpc-%{mpc_version}.tar.gz
> >     <http://www.multiprecision.org/mpc/download/mpc-%{mpc_
> version}.tar.gz>
> >     > +%source set mpc https://ftp.gnu.org/gnu/mpc/
> mpc-%{mpc_version}.tar.gz
> >     <https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz>
> >
> >     This does not work for 4.10 as GNU only hosts mpc-1.0.1 and later
> and 4.10 uses
> >     0.8.1.
> >
> >     Do we update MPC etc to use GNU hosted version?
> >
> >
> > That seems potentially dangerous. It could unintentionally change the
> toolset
> > behavior.
>
> I do not know. It would depend on how this package is used in gcc-4.4.7.
>
> >
> > What was the recommended version with that GCC version? Any idea?
> >
>
> I do not know.
>
> > Can we host the required version? Isn't it already on our ftp site since
> you
> > unrolled all the source RPMs?
>
> We host all source in a release on the RTEMS FTP site as part of the
> release and
> RSB releases know to use the RTEMS FTP site by default. The issue is
> creating a
> releases requires the source be present on the project's specified home
> site.
> This means we cannot make a release if the source cannot be found.
>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180117/5d393eb2/attachment-0002.html>


More information about the devel mailing list