Hello. While trying to get base PLD Titanium working I've encountered serious problem with rpm and I can't find what causes it. Any help or hints will be appreciated. Situation (in chronological order):
1. rpm 4.4.9-1 was built manually in PLD Ac amd64 chroot after hacking macros to force usage of x86-64 gcc. Everything works. 2. After installing resulting packages same rpm was rebuild once again to see if it will work without hacking macros. It worked and rpm still works at this point 3. Now following things were done: perl was updated from AC-branch to HEAD one. OpenSSL was upgraded to 0.9.8. Python and poldek were rebuilt with new openssl. 4. At some point I've tried to build mawk.spec and got following error from builder: Documentation compressed. + exit 0 -bash: line 1: 28157 Segmentation fault TMPDIR=/tmp/B.c49d5d nice -n 19 rpmbuild -bb --target x86_64-pld-linux mawk.spec error: No files produced. I've tried manual build and got: Documentation compressed. + exit 0 Memory fault (core dumped) Error: package build failed. (no more info) gdb says: Core was generated by `rpmbuild -ba -v mawk.spec'. Program terminated with signal 11, Segmentation fault. #0 0x00002ac399dbd165 in _start () from /lib64/ld-linux-x86-64.so.2 (gdb) bt #0 0x00002ac399dbd165 in _start () from /lib64/ld-linux-x86-64.so.2 #1 0x0000000000000000 in ?? () So it seems like glibc problem, but glibc wasn't touched and at point 2 same spec was building just fine. 5. What I've tried to fix the problem: a) I recompiled both glibc and rpm with debugging symbols but gdb still wasn't giving more information than above. b) I've upgraded rpm to 4.4.9-9, no change. c) I've upgraded glibc from 2.6.1-2 to 2.6.1-3 d) I've adjusted and tried http://rpm5.org/cvs/chngview?cn=7926 patch to see if its BUFSIZ problem. Still no luck. 6. Problem exists only on x86_64 platform. i586 and i686 are working OK. 7. currently x86_64 version of PLD Titanium is just PLD Ac amd64 with just few core packages rebuilt to x86_64 arch. 8. Other failing specs are perl and rpm-build-macros Any ideas what more I can do to nail this problem? If you need more info let me know. M. _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
