On Fri, Mar 20, 2020 at 7:56 PM Joel Sherrill <j...@rtems.org> wrote:

> Hi
>
> I think something is wrong with the build of spike that ends up with
> a hard-coded path to inside a build tree:
>
> Result: invalid    Time: 0:00:01.197748 mimfs_fslink.exe
> =>  run: spike --isa=RV32IAC 
> ./riscv-rtems5/c/rv32iac/testsuites/fstests/mimfs_fslink.exe
> ] Failed to run 
> /home/joel/rtems-cron-5/rtems-source-builder/bare/build/tmp/sb-1001/devel/spike/home/joel/rtems-cron-5/tools/5/bin/dtc:
>  No such file or directory
> ] Child dtb process failed
>
> https://lists.rtems.org/pipermail/build/2020-March/011112.html
>
> Does spike work if there isn't this problem?
>
> I can poke at the host exes to see if the dtc path is hard-coded. Otherwise, 
> this seems very strange.
>
>
I can confirm that spike built with the RSB has the hard-coded
path to dtc that is in the temporary RSB build/staging directories.

$ strings spike | grep dtc
/home/joel/rtems-cron-5/rtems-source-builder/bare/build/tmp/sb-1001/devel/spike/home/joel/rtems-cron-5/tools/5/bin/dtc
Failed to run
/home/joel/rtems-cron-5/rtems-source-builder/bare/build/tmp/sb-1001/devel/spike/home/joel/rtems-cron-5/tools/5/bin/dtc:

> Any ideas?
>
> --joel
>
>
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to