Can you supply a backtrace and a ptr to module-init-tools-3.2.2-ian1.5.2.src.rpm? A bug report at http://bugzilla.redhat.com against rpm is likely best, lest we be boring ;-) 73 de Jeff On 3/20/07, Aggelos Manousarides <amanous@xxxxxxxxxxxxxxxxxxxx> wrote:
I am using the RPM to build binary packages with cross compilers. I have a set of scripts which compile and install RPM on a separate path under /opt. These scripts so far have managed to produce a valid RPM installation on a lot of different systems. Old glibc's, old kernels, whatever. The combination of software is: rpm-4.4.5 beecrypt-4.1.2 neon-0.25.5 The other libraries are from the system (libexpat, zlib, bz2, etc). I tried to do the same on a new server and rpm segfaults while installing a source RPM. I have not yet configured a database or anything. Just installing a source RPM causes this behavior: ************************************ $ rpm -ivv module-init-tools-3.2.2-ian1.5.2.src.rpm D: ============== module-init-tools-3.2.2-ian1.5.2.src.rpm D: Expected size: 171986 = lead(96)+sigs(180)+pad(4)+data(171706) D: Actual size: 171986 D: module-init-tools-3.2.2-ian1.5.2.src.rpm: Header SHA1 digest: OK (4d4bec05aae705830dbb4973d98561e133384f1b) D: added source package [0] D: found 1 source and 0 binary packages D: Expected size: 171986 = lead(96)+sigs(180)+pad(4)+data(171706) D: Actual size: 171986 D: InstallSourcePackage: Header SHA1 digest: OK (4d4bec05aae705830dbb4973d98561e133384f1b) module-init-tools-3.2.2-ian1.5.2 D: ========== Directories not explicitly included in package: D: 0 /home/amanous/rpm/build/SOURCES/ D: 1 /home/amanous/rpm/build/SPECS/ D: ========== Segmentation fault ************************************ This server is a dual quad-core XEON with 8GB RAM. I have installed RPM successfully on SMP machines before without any problems. The operating system is ubuntu edgy (6.10), the compiler gcc 4.1.2. I have to note that the rpm provided by ubuntu is 4.4.1 with the same versions of neon and beecrypt libraries, and it works fine. Are there any changes between 4.4.1 and 4.4.5 that might cause this? Do I need any extra patches for gcc-4.x or glibc-2.4? So far the systems I have tried where gcc-3.x and glibc-2.3.x. -- Angelos Manousaridis _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
