Hi,

After updating to the latest git tree of ptxdist yesterday I can no
longer build a correct root file system,

During the targetinstall phase when the ipk package is being build I
get a error / warning from tar that the file that is being packaged
has changed during reading,
see below for several of these warnings

tar: ./usr/lib/libusb-0.1.so.4: file changed as we read it
tar: ./usr/lib/libstdc++.so.6: file changed as we read it
tar: ./lib/libpthread.so.0: file changed as we read it
tar: ./lib/libc.so.6: file changed as we read it
tar: ./lib/libdl.so.2: file changed as we read it
tar: ./usr/lib/libnss_compat.so: file changed as we read it
tar: ./usr/lib/libutil.so: file changed as we read it
tar: ./usr/lib/libnss_dns.so: file changed as we read it
tar: ./usr/lib/libresolv.so: file changed as we read it
tar: ./usr/lib/libnss_nis.so: file changed as we read it
tar: ./usr/lib/libm.so: file changed as we read it
tar: ./usr/lib/libnsl.so: file changed as we read it
tar: ./usr/lib/libnss_files.so: file changed as we read it
tar: ./usr/lib/librt.so: file changed as we read it
tar: ./usr/lib/libnss_nisplus.so: file changed as we read it
tar: ./usr/lib/libdl.so: file changed as we read it
tar: ./usr/lib/libnss_hesiod.so: file changed as we read it

These warnings result for me in a root file system that no longer
boots (kernel panic /lib/libc.so.6 file too short)

When looking at the package that is created instead of the expected
symbolic link the package contains an unreadable elf file with the
same file size as the symbolic link, so that would explain the kernel
panic.

I think the problems originates somewhere in ipkg-build step, but I'm
not sure how to track it any further. Any help would be appreciated.

Regards,
Bart vdr. Meulen

--
ptxdist mailing list
[email protected]

Reply via email to