On Wed, Jun 6, 2018 at 11:12 PM, Chris Johns <chr...@rtems.org> wrote: > On 07/06/2018 03:55, Gedare Bloom wrote: >> On Tue, Jun 5, 2018 at 9:02 PM, Chris Johns <chr...@rtems.org> wrote: >>> On 31/5/18 2:56 am, Gedare Bloom wrote: >>> >>> Is this still only with a concurrent build? >>> >> >> I think this was without concurrent build. >> > > Then I suspect this is the space in the path. > >>>> make[4]: Entering directory '/media/gedare/Seagate Expansion >>>> Drive/work/rtems/builds/b-erc32-5/sparc-rtems5/c/erc32/lib/libbsp' >>> >>> I wonder if some of the internal shell script processing we have is safe >>> with a >>> space in a path? >>> >> >> It is possible. I've had problems before with spaces in the path using >> RSB and rtems-test tools. I haven't had trouble before with >> configure/make though. >> > > The base autoconf and automake should be clean but we have a range of scripts > and m4 fragments that may not be. >
OK, and I concur with your assessment. It worked a couple months ago. I might try to bisect if I have time. I would bet something in our scripts that changed during the source code reorg causes the problem. > Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
