>>>> severity 655801 important >>>> thanks >>>> >>>> I can't reproduce the bug. So I reduce severity level. >> >>> I can. Please post a build log including dependencies installation, so >>> we can see why lua is there for you but not for me. >> >> I think that Your filesystem is a cause for Your trouble.
> Can you elaborate ? >> buildlog for i386: >> >> https://buildd.debian.org/status/fetch.php?pkg=tarantool&arch=i386&ver=1.4.4%2B20120127-1&stamp=1327746838 > In your log: > make[4]: Entering directory > `/build/buildd-tarantool_1.4.4+20120127-1-i386-v48zmd/tarantool-1.4.4+20120127/build-area/third_party/luajit/src' > HOSTCC buildvm.o > gcc -O2 -fomit-frame-pointer -Wall -c -o buildvm.o buildvm.c > HOSTCC buildvm_asm.o > gcc -O2 -fomit-frame-pointer -Wall -c -o buildvm_asm.o > buildvm_asm.c > [...] > In my log: > make[4]: Entering directory > `/«BUILDDIR»/tarantool-1.4.4+20120127/build-area/third_party/luajit/src' > DYNASM buildvm_ppcspe.h > lua ../dynasm/dynasm.lua -D SPE -o buildvm_ppcspe.h buildvm_ppc.dasc > make[4]: lua: Command not found > make[4]: *** [buildvm_ppcspe.h] Error 127 > Can you explain that difference? I think that Your tar unpacked buildvm_ppcspe.h after buildvm_ppc.dasc and set wrong date for the file. The project contains some parts that are prebuilt by hand, for example some ragel c-objects and the case. But they aren't compiled if You unpack tarball correctly. I can reproduce Your problem only If I change datetime some files by hand. -- . ''`. Dmitry E. Oboukhov : :’ : email: un...@debian.org jabber://un...@uvw.ru `. `~’ GPGKey: 1024D / F8E26537 2006-11-21 `- 1B23 D4F8 8EC0 D902 0555 E438 AB8C 00CF F8E2 6537
signature.asc
Description: Digital signature
