On 28/9/2022 11:42 pm, Christian MAUDERER wrote: > Hello, > > with this patch, I don't get a tar for devel/qemu and for the > 6/rtems-microblaze > anymore. All other 6/rtems-* toolchains work without problems. I haven't > tested > a lot of the other packages. > > The bset for microblaze is a bit different from the other ones. But I'm not > yet > sure what the relevant difference is. > > @Chris: With your change: What is necessary that a bset can generate a tar > archive?
It could be a bug if the tools builds work, ie 6/rtems-*. Please raise a ticket? I changed the --bset-tar-file option to create a single tarfile of the final staged output of a build. There were a few commits to get this right so I assume you are testing on the latest? Incremental tarfiles based on separate buildsets in a buildset may have worked in some cases however there were some basic issues in how it was implemented. When you add deployment requirements on top it did not match up well and it was confusing. The best solution was to rebase the tarfile against the final staged output as that is known to be correct in all cases. I have created a https://git.rtems.org/chrisj/rtems-deployment.git repo and in it a config test directory (https://git.rtems.org/chrisj/rtems-deployment.git/tree/config/test). I will look at adding a test to make sure we catch any issues. Thanks Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel