On Tue, Sep 5, 2017 at 1:41 PM, Jacob Saina <jsa...@terpmail.umd.edu> wrote:
> Hi Chris, > > I checked out "4.11" from the git repository, and did the following with > Internet: > > ~/workspace/rsb/rtems$ ../source-builder/sb-set-builder --dry-run > --with-download --without-error-report --without-release-url > --prefix=/home/jsaina/rtems/4.11 4.11/rtems-arm > > Then I disconnected my network cable and did: > > ~/workspace/rsb/rtems$ ../source-builder/sb-set-builder > --prefix=/home/jsaina/rtems/4.11 4.11/rtems-arm > > This fails as follows: > ... > > reporting: tools/rtems-gdb-7.9-1.cfg -> arm-rtems4.11-gdb-7.9-x86_64- > linux-gnu-1.xml > config: tools/rtems-tools-4.11-1.cfg > package: rtems-tools-4.11-1 > git: reset: git://git.rtems.org/rtems-tools.git > git: fetch: git://git.rtems.org/rtems-tools.git -> > sources/git/rtems-tools.git > error: git command failed (/usr/bin/git): 128 > Build FAILED > See error report: rsb-report-rtems-tools-4.11-1.txt > error: git command failed (/usr/bin/git): 128 > Build Set: Time 1:10:37.113829 > Build FAILED > > What am I misunderstanding? > Looks like things that are fetched from git have an issue with the predownload. Chris.. is there a way to check that the existing git checkout is in the right state before operating on it? If we still need to support cvs or svn, they might have the same issue. --joel > Thanks for your help, > > Jacob > > On Fri, Sep 1, 2017 at 6:49 PM, Chris Johns <chr...@rtems.org> wrote: > >> On 2/9/17 3:38 am, Jacob Saina wrote: >> > >> > I'm going to be building rsb, rtems, and applications with an >> intermittent >> > Internet connection, so I'd like to have all the pieces in place on disk >> > beforehand. How can I pull down all the necessary files and avoid >> failing >> > because of network access? >> >> To fetch the packages use: >> >> ../source-builder/sb-set-builder \ >> --dry-run --with-download \ >> --without-error-report \ >> --without-release-url \ >> 4.12/rtems-arm >> >> Replace '4.12/rtems-arm' with the build set you want to build. This >> command >> comes from the release scripts [1]. >> >> You should be able to move the 'source' and 'patch' contents to another >> location >> on you disk and then use the '--url' option with 'file://path'. >> >> Chris >> >> [1] https://git.rtems.org/rtems-release/tree/rtems-release-sources#n112 >> > > > _______________________________________________ > users mailing list > users@rtems.org > http://lists.rtems.org/mailman/listinfo/users >
_______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
