2012/5/26 Kornel Benko <kor...@lyx.org>: > Am Samstag, 26. Mai 2012 um 16:41:45, schrieb Eric Noulard > <eric.noul...@gmail.com>
>> dpkg -c xyzzy.deb > This gives the standard tar ztvf output from data.tar.gz, could not see > anything special there. > One thing though is the definition of owner/group of all listed files. > In the "working" version, this is kornel/kornel, in the "bad" version it is > root/root; Ok, this is the 'automatic' fakeroot effect. I don't think it's the cause of the problem anyway. >> Would you be able to try with prebuilt cmake-2.8.8 from kitware: >> you can untar this archive >> http://www.cmake.org/files/v2.8/cmake-2.8.8-Linux-i386.tar.gz > > Yes, but I fear, it is not cmake but cpack. Yes right off course. But since you said you use make package I guessed you'll used cmake + cpack for the whhole build+package process. > ... > As I expected, replacing the cpack binary cured everything. > The BIG difference is > #ldd /mnt/usr2/src/cmake/cmake-2.8.8-Linux-i386/bin/cpack > linux-gate.so.1 => (0xf7761000) > libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf771d000) > libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf76f1000) > libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf754b000) > /lib/ld-linux.so.2 (0xf7762000) > > while > #ldd /usr/bin/cpack > display 45 different shared libraries, among them also > libarchive.so.12 => /usr/lib/x86_64-linux-gnu/libarchive.so.12 > (0x00007fd16c52e000) It could be they must have ticked "CMAKE_USE_SYSTEM_LIBARCHIVE" and may be other CMAKE_USE_SYSTEM_xxxx. It should be harmless but who knows. > which I suspect to be the one creating trouble ... > >> and use cmake with full path from there. >> (May be some ubuntu specific patch are playing behind our back??) >> >> Last but not least may be the automatic usage of fakeroot is the culprit, >> In order to check that could you >> 1) uninstall fakeroot (aptitude remove fakeroot) > > Sorry, this one has tried to remove 468 other packages while leaving also > next 126 packages > with unresolved dependencies. So I prefer not to follow. Yes no problem like I said this one shouldn't be the source of the problem. I'll try to add something in order to be able to disable this in the future. >> In any case if kitware pre-compiled binary failed you should file a bug >> report on the tracker. >> > > As I wrote, this one works. Then I guess you should file a bug to ubuntu package maintainer. -- Erk Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org -- 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://www.cmake.org/mailman/listinfo/cmake