Building toolset for Beaglebone with RSB fails (for me).

[Joel Sherrill]

GCC does not keep snapshots forever. Ben's instructions and git repo must
be behind the master at git.rtems.org. clone the repos from there, use the
master, and I believe his instructions will work.

Ben.. if you see this, maybe it is time to.merge some of your instructions
into the new Sphinx documentation in a section for BB users.

--joel

On Feb 10, 2017 2:04 PM, "Tanu Hari Dixit" <tokencolour at gmail.com> wrote:

> Hello Devs,
>
> I wanted to build the toolset for Beaglebone following the blog (
> http://www.shrike-systems.com/beagleboard-xm-beaglebone-
> black-and-everything-else-rtems-on-the-beagles.html).
> However, the build failed.
> I got the following message.
>
> download: ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6-
> 20160526.tar.bz2 -> sources/gcc-6-20160526.tar.bz2
> download: ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6-
> 20160526.tar.bz2: error: <urlopen error ftp error: 550
> pub/gcc/snapshots/6-20160526: No such file or directory>
> error: downloading ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6-
> 20160526.tar.bz2: all paths have failed, giving up
> Build FAILED
>   See error report: rsb-report-arm-rtems4.12-gcc-6-20160526-newlib-2.4.0.
> 20160527-x86_64-linux-gnu-1.txt
> error: downloading ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6-
> 20160526.tar.bz2: all paths have failed, giving up
> Build Set: Time 0:01:46.366099
> Build FAILED
>
> Probably, the link is broken.
>
> It is probably using rtems-source-builder/rtems/config/tools/rtems-gcc-6-
> 20160526-newlib-2.4.0.20160527-1.cfg
> which sets this url which ultimately is used by
> rtems-source-builder/source-builder/config/gcc-common-1.cfg . Please
> correct me if I am wrong.
>
> How do I fix this? Is there something I am missing?
>
> Thanks,
> Tanu Hari Dixit.
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20170210/022ea55b/attachment-0002.html>