CMake 2.8.12-rc3 cannot extract these .tar.gz files via "cmake -E tar xzf":

   https://github.com/zeromq/zeromq3-x/archive/v3.2.2.tar.gz
   https://github.com/zeromq/zeromq3-x/archive/v3.2.3.tar.gz
   https://github.com/zeromq/zeromq3-x/archive/master.tar.gz

But this is not a recent (if at all) regression, 2.8.10 and 2.8.11 also fail to extract them...

There's also an error if trying to extract the equivalent .zip files (replace .tar.gz with .zip in the URLs...)

It is always on the same file, doc/zmq_epgm.txt, with output like this:

-- extracting... [tar xfz]
CMake Error: Problem with archive_write_header(): Can't create '\\?\C:...\src\ex-download-zeromq1234\zeromq3-x-3.2.3\doc\zmq_epgm.txt'
CMake Error: Current file: zeromq3-x-3.2.3/doc/zmq_epgm.txt
CMake Error: Problem extracting tar: C:/.../Downloads/zeromq3-x-v3.2.3.tar.gz
-- extracting... [error clean up]
CMake Error at C:/.../download-zeromq-prefix/src/download-zeromq-stamp/extract-download-
zeromq.cmake:33 (message):
 error: extract of 'C:/.../Downloads/zeromq3-x-v3.2.3.tar.gz'
 failed

CMake bug? Libarchive bug? Maybe fixed already upstream?

One more tidbit: 7-zip *can* extract the archives just fine, so I don't think there's anything unrecoverably wrong with the archive files themselves.

Anybody have a quick fix or a workaround I can use?

(I'm not a fan of using 7-zip for the extraction, or of using "git" snapped to a tag: I'm trying to make a super build work with just cmake -E and .tar.gz files. If I must, I'll simply create a new tar.gz without the file that's making it choke, and use that... I'd really prefer to use the "official" one from github, though. So I don't have to host a custom one anywhere...)


Thanks,
David C.

--

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