You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a long trial and error period with @fhunleth we decided we needed to keep toolchains in xz compression which is not supported by erl_tar. This requires us to continue to shell out to tar. I am updating the description of this task to redirect it towards a conversation about xz and windows
mobileoverlord
changed the title
use :erl_tar instead of tar command
Discuss xz support for all platforms
Jan 19, 2016
mobileoverlord
changed the title
Discuss xz support for all platforms
Discuss xz support for platforms
Jan 19, 2016
The reason for not using erl_tar was that it failed to extract the toolchain tarballs. The initial problem was that we are using GNU Tar to create the tarballs. Upon review of the erl_tar docs, we started specifying --format=ustar when calling GNU Tar. This created the additional problem of restricting path lengths too much to include a couple files for the crosscompiler. An attempt was made to make a root directory-less tarball so that the path length constraint could be met, but this prevented Buildroot from using the toolchain.
This is required especially for windows support.
The text was updated successfully, but these errors were encountered: