Bugzilla – Bug 144122
cvsup starts with a segmentation fault and can not be compiled
Last modified: 2006-04-25 08:36:29 UTC
The tool "cvsup" does not start on SuSE Linux 10.1 Beta 1. Instead it starts with a segmentation fault: $ cvsup Speicherzugriffsfehler (English: segmentation fault, the message is German, also with LC_ALL=C ?) My cvsup comes from package cvsup-16.1h-176.i586.rpm. Since I can not find the source rpm of cvsup in the SuSE OSS factory directory, I tried to compile cvsup from SuSE Linux 10.0. Unfortunately also compilation of cvsup failes with an segmentation fault. $ rpmbuild --rebuild cvsup-16.1h-175.src.rpm [...] cc -o m3ship Main_m.o _m3main.o ../../m3config/LINUXLIBC6/libm3config.a ../../m3templates/LINUXLIBC6/libm3templates.a ../../m3driver/LINUXLIBC6/libm3driver.a ../../m3linker/LINUXLIBC6/libm3link.a ../../m3front/LINUXLIBC6/libm3front.a ../../m3quake/LINUXLIBC6/libm3quake.a ../../m3middle/LINUXLIBC6/libm3middle.a ../../libm3/LINUXLIBC6/libm3.a ../../m3core/LINUXLIBC6/libm3core.a -lm make[1]: Leaving directory `/var/soft/BUILD/cvsup-snap-16.1h/ezm3-1.1/boot-LINUXLIBC6/m3ship/LINUXLIBC6' boot-LINUXLIBC6/m3build/LINUXLIBC6/m3build -T ../m3config/src -DBOOTSTRAP=TRUE make: *** [packages] Speicherzugriffsfehler error: Bad exit status from /var/tmp/rpm-tmp.72242 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.72242 (%build)
I get the same compilation error with the original distribution ftp://ftp.freebsd.org/pub/FreeBSD/development/CVSup/ezm3/ezm3-1.2-LINUXLIBC6-boot.tar.bz2 ftp://ftp.freebsd.org/pub/FreeBSD/development/CVSup/ezm3/ezm3-1.2-src.tar.bz2
Hello Bjoern, is the package you're using an officially shipped SUSE packages, because this package was dropped for 10.1 - what version of SUSE Linux are you using exactly?
Yes, I saw, that cvsup is not part of SuSE Linux 10.1 Alpha4 and Beta1. But it was probably part of earlier alpha versions of SuSE 10.1. I attach my "rpm -qi" info from cvsup-16.1h-176 package. The maintainer John Polsta <jdp at polstra dot com> responded to my mail: > It's probably caused by a change to glibc. Ezm3 is pretty > intolerant of changes to libc data structures. Unfortunately, I'm > the entire "team", and I don't have time anymore to maintain Ezm3 and > CVSup very actively. So, I'm sorry, but it's unlikely I will fix > this problem. I would like to see a working cvsup package in 10.1, because I relative often need cvsup. Unfortunately I don't know Modula3 and can't help very much myself.
Created attachment 64423 [details] cvsup rpm package info
i will close the bug now. kraxel: is there maybe a replacement for cvsup on 10.1? please reopen if you think you can help out here. Björn: when the problem is also in upstream i guess there is not much we can do when the package is already dropped.
cvsup was dropped due to legal reasons and due to everybody slowly switching away from cvs to something else as version control system. Very unlikely it comes back, especially given this new build problem. The old binaries should continue to work though ...
Yes, but CVSUP and CVS is not fully the same. CVSUP is much faster for people, which only want to update their sources. The old binaries DO NOT WORK with SuSE Linux 10.1 (see above).
Just a tip for CVSup users: - there is a CVSup rewrite in C called CSup: http://www.mu.org/~mux/csup.html - CSup compiles on SuSE Linux - in my tests the CVSup checkout with CSup worked fine - my attached patch makes CSup's GNUmakefile a bit more usable (patch against CSup's CVS HEAD)
Created attachment 79810 [details] Patch for CSup (not CVSup) This patch makes the GNUmakefile from CSup a bit more usable.