On 2012年04月27日 08:17, Cole Robinson wrote:
In building the libvirt-0.9.11.2 stable tarball, I saw these errors:
tar: libvirt-0.9.11.2/tests/nodeinfodata/linux-nodeinfo-sysfs-test-1/cpu/cpu0/topology/thread_siblings_list: file name is too long (max 99); not dumped tar: libvirt-0.9.11.2/tests/nodeinfodata/linux-nodeinfo-sysfs-test-1/cpu/cpu0/topology/physical_package_id: file name is too long (max 99); not dumped tar: libvirt-0.9.11.2/tests/nodeinfodata/linux-nodeinfo-sysfs-test-1/cpu/cpu1/topology/thread_siblings_list: file name is too long (max 99); not dumped tar: libvirt-0.9.11.2/tests/nodeinfodata/linux-nodeinfo-sysfs-test-1/cpu/cpu1/topology/physical_package_id: file name is too long (max 99); not dumped tar: Exiting with failure status due to previous errors
As indicated the files were not in the tarball.
Can we just update the tar format in configure or does that come with caveats?
<quote> tar-ustar selects the ustar format defined by POSIX 1003.1-1988. This format is believed to be old enough to be portable. </quote> Using 'tar-ustar'? Regards, Osier