On Thu, Jun 18, 2009 at 5:31 AM, Bruno Haible<[email protected]> wrote: > Sam Steingold wrote: >> >> after: >> >> $ grep -i sigsegv config.status >> >> S["LIBSIGSEGV_PREFIX"]="" >> >> S["LTLIBSIGSEGV"]="" >> >> S["LIBSIGSEGV"]="" >> >> S["HAVE_LIBSIGSEGV"]="yes" >> >> D["HAVE_LIBSIGSEGV"]=" 1" >> >> D["HAVE_LIBSIGSEGV"]=" 1" >> >> >> ... >> > $ ls -l /usr/include/sigsegv* /usr/lib*/libsigsegv* >> >> >> 8 -rw-r--r-- 1 root root 5802 Sep 17 2008 /usr/include/sigsegv-x86_64.h >> 4 -rw-r--r-- 1 root root 733 Aug 15 2008 /usr/include/sigsegv.h >> 0 lrwxrwxrwx 1 root root 19 Jun 15 17:35 /usr/lib64/libsigsegv.so >> -> libsigsegv.so.0.0.0* >> 0 lrwxrwxrwx 1 root root 19 Jun 15 17:34 /usr/lib64/libsigsegv.so.0 >> -> libsigsegv.so.0.0.0* >> 12 -rwxr-xr-x 1 root root 9440 Sep 17 2008 /usr/lib64/libsigsegv.so.0.0.0* > > Hmm. I cannot reproduce.
I am not alone. <http://thread.gmane.org/gmane.lisp.clisp.devel/20175> > I suspect it has something to do with the autoconf infrastructure of your > package. Can you provide a complete tarball of it? (The clisp cvs still has > libsigsegv.m4 serial 3.) I reverted back to serial 3 so that my users can build. try "cvs up -D 2009-06-16" -- Sam Steingold <http://sds.podval.org>
