For 4.10, the tools are on a different track than the master. They are frozen to older tools.
The URL has a few issues: + rtems.com reference should be rtems.org + After the hosting moved to OSU OSL, we went from one IP address for all machines to a unique name/IP per service. So www.rtems.org != ftp.rtems.org + ftp site reorganization + that SOURCES directory was based on the assumption RTEMS provided RPMs for tools and that directory got updated. Taken all together, look here: https://ftp.rtems.org/pub/rtems/releases/4.10/tools/ It looks like a newer newlib patch is there. But I would just use those as a reference and try to build from the RTEMS git master with new tools. --joel On Thu, May 19, 2016 at 5:12 PM, Gedare Bloom <ged...@rtems.org> wrote: > I believe those patches aren't needed any more, as we have worked to > submit our patches upstream and use newlib snapshots and releases > directly. You should refer to the source versions identified by the > RSB, and see whether it applies any patches, to understand what source > it compiles to build a tool chain. > > Gedare > > On Thu, May 19, 2016 at 7:23 AM, Sambeet Panigrahi > <sambeet161...@gmail.com> wrote: > > Hi, > > I was going through the old scripts o porting Rock on RTEMS.While > building > > the rtems version 4.10.1 a patch was used namely > > > > > http://www.rtems.com/ftp/pub/rtems/SOURCES/4.10/newlib-1.18.0-rtems4.10-20110518.diff > > > > This url gives a page not found error now. I am now modifying the scripts > > for rtems4.11.Where can I find the necessary patches? I don't want to > use th > > RSB now so that i understand the building procedure step by step. Can > > someone help? > > regards > > Sambeet >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
