Am Dienstag, 5. Juni 2012 um 16:43:15, schrieb Brad King <[email protected]>
> On 06/05/2012 03:55 PM, Kornel Benko wrote:
> > Ok, I created a dir with 340 entries. (330 entries was not enough).
> 
> Thanks.  I see the header in the tarball you sent:
> 
>  $ tar xvzf ../data.tgz |wc -l
>  tar: Ignoring unknown extended header keyword `SCHILY.fflags'
>  341
> 
> However, I cannot reproduce it.  I built libarchive 3.0.3 from
> upstream and built CMake 2.8.8 against it:

>  $ tar --version
>  tar (GNU tar) 1.26
>  $ .../bin/cmake --version
>  cmake version 2.8.8
>  $ ldd .../bin/cmake |grep libarchive
>          libarchive.so.12 => .../lib/libarchive.so.12 (0x00007fd4a999a000)
>  $ strings .../lib/libarchive.so.12 |grep 3.0
>  libarchive 3.0.3

Same tar version here.

> I can create a tarball from the same directory extracted from yours
> and it has no trouble:

Not nice, isn't it?

>  $ .../bin/cmake -E tar cf xx.tar xx
>  $ tar xvf xx.tar |wc -l
>  341
> I can make a much bigger one without trouble too:
> 
>  $ for n in $(seq 1 4096); do echo $n > xx/$n; done
>  $ .../bin/cmake -E tar cf xx.tar xx
>  $ tar xvf xx.tar |wc -l
>  4097

I can do this too, but only if explicitly called
# cmake -E tar cf xx.tar xx/*
==> ok
but
# cmake -E tar cf xx.tar xx
==> error in xx.tar

> Is there any change in Ubuntu's package for libarchive that is
> not upstream?

I don't know, but it would surprise me ...
Maybe it is one of the underlying libs, like libattr.so.1 or libnettle.so.4 . 
This guessing makes me not happy.
#ldd /usr/lib/x86_64-linux-gnu/libarchive.so.12.0.3
        linux-vdso.so.1 =>  (0x00007fff197ff000)
        libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 (0x00007f693958a000)
        libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 (0x00007f6939385000)
        liblzma.so.5 => /usr/lib/x86_64-linux-gnu/liblzma.so.5 
(0x00007f6939162000)
        libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x00007f6938f52000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f6938d3b000)
        libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 
(0x00007f69389df000)
        libnettle.so.4 => /usr/lib/x86_64-linux-gnu/libnettle.so.4 
(0x00007f69387b9000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f69383fc000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x00007f69381de000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6937fda000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6937ce0000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f6939a5b000)



> This may also depend on the filesystem.

EXT3

> Are you using selinux?

The selinux libraries are installed, but selinux and selinux-basics are not, so
the answer should be "no".

> -Brad

        Kornel

Attachment: signature.asc
Description: This is a digitally signed message part.

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers

Reply via email to