BUG: SIGSEGV in clisp build

[yaseppochi (Stephen J. Turnbull)]

Looks like upstream breakage. Output from port upgrade follows. Bon apetit!

papa% port upgrade -u clisp curl zsh postgresql Usage: port [-vdqfonasbcktu] [-D portdir] action [actionflags] [[portname|pseudo-portname|port-url] [@version] [+-variant]... [option=value]...]...

"port help" or "man 1 port" for more information. papa% port -u upgrade clisp curl zsh postgresql ---> Fetching libsigsegv ---> Attempting to fetch libsigsegv-2.1.tar.gz from ​ftp://ftp.gnu.org/gnu/libsigsegv ---> Verifying checksum(s) for libsigsegv ---> Extracting libsigsegv ---> Applying patches to libsigsegv ---> Configuring libsigsegv ---> Building libsigsegv with target all ---> Staging libsigsegv into destroot ---> Packaging tgz archive for libsigsegv 2.1_0 ---> Installing libsigsegv 2.1_0 ---> Activating libsigsegv 2.1_0 ---> Cleaning libsigsegv ---> Fetching clisp ---> Attempting to fetch clisp-2.36.tar.gz from ​ftp://ftp.gnu.org/gnu/clisp/release/2.36 ---> Verifying checksum(s) for clisp ---> Extracting clisp ---> Applying patches to clisp ---> Configuring clisp ---> Building clisp with target all Error: Target com.apple.build returned: shell command "CPPFLAGS=-I/opt/local/include LDFLAGS=-L/opt/local/lib make" returned error 2 Command output: Copyright (c) Sam Steingold, Bruno Haible 2001-2005

;; Loading file defseq.lisp ... ;; Loaded file defseq.lisp ;; Loading file backquote.lisp ... ;; Loaded file backquote.lisp ;; Loading file defmacro.lisp ... ;; Loaded file defmacro.lisp ;; Loading file macros1.lisp ... ;; Loaded file macros1.lisp ;; Loading file macros2.lisp ... ;; Loaded file macros2.lisp ;; Loading file defs1.lisp ... ;; Loaded file defs1.lisp ;; Loading file lambdalist.lisp ... ;; Loaded file lambdalist.lisp ;; Loading file places.lisp ... ;; Loaded file places.lisp ;; Loading file floatprint.lisp ... ;; Loaded file floatprint.lisp ;; Loading file defpackage.lisp ... ;; Loaded file defpackage.lisp ;; Loading file type.lisp ... ;; Loading file subtypep.lisp ... * - handle_fault error2 ! address = 0x0 not in [0x1a800000,0x1a839dd0) ! SIGSEGV cannot be cured. Fault address = 0x0. Permanently allocated: 88864 bytes. Currently in use: 809352 bytes. Free space: 497500 bytes. make: * [interpreted.mem] Bus error

Error: Unable to upgrade port: 1

[blb@…]

Assign to maintainer.

[gwright@…]

I'll take a look. Thanks.

/Greg

[bgmnt@…]

Similar problem here (OS X 10.3.9, fresh XCode 1.5 install): ========================================================= ---> Fetching clisp ---> Verifying checksum(s) for clisp ---> Extracting clisp ---> Applying patches to clisp ---> Configuring clisp ---> Building clisp with target all Error: Target com.apple.build returned: shell command "CPPFLAGS=-I/opt/local/include LDFLAGS=-L/opt/local/lib make" returned error 1 Command output: ;; Datei defseq.lisp wird geladen... ;; Datei defseq.lisp ist geladen. ;; Datei backquote.lisp wird geladen... ;; Datei backquote.lisp ist geladen. ;; Datei defmacro.lisp wird geladen... ;; Datei defmacro.lisp ist geladen. ;; Datei macros1.lisp wird geladen... ;; Datei macros1.lisp ist geladen. ;; Datei macros2.lisp wird geladen... ;; Datei macros2.lisp ist geladen. ;; Datei defs1.lisp wird geladen... ;; Datei defs1.lisp ist geladen. ;; Datei lambdalist.lisp wird geladen... ;; Datei lambdalist.lisp ist geladen. ;; Datei places.lisp wird geladen... ;; Datei places.lisp ist geladen. ;; Datei floatprint.lisp wird geladen... ;; Datei floatprint.lisp ist geladen. ;; Datei defpackage.lisp wird geladen... ;; Datei defpackage.lisp ist geladen. ;; Datei type.lisp wird geladen... * - handle_fault error2 ! address = 0x0 not in [0x1a800000,0x1a839f6c) ! SIGSEGV cannot be cured. Fault address = 0x0. Permanently allocated: 88864 bytes. Currently in use: 1218360 bytes. Free space: 516 bytes. * Signal 10

Stop in /opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.127.0.0.1:8730_dpupdate_dports_lang_clisp/work/clisp-2.36/src.

Error: /opt/local/bin/port: Status 1 encountered during processing.

[gwright@…]

I have just committed a portfile for clisp 2.37. The default is now to build without dynamic foreign function support, and to not use libsigsegv on Panther (10.3.x). If you have installed libsigsegv, you need to uninstall it before rebuilding clisp. (There is no way to tell clisp's configure script _not_ to use libsigsegv if it finds it installed.)

To turn on dynamic ffi support, use the +dynffi variant. To build without libsigsegv support on Tiger, uninstall libsigsegv and use the +nolibsigsegv variant.

All combinations of variants build and pass all tests on my powerbook G4, 1 GB, OS X 10.4.3, Xcode 2.2 system. I hope that disabling dynamic ffi support and not using libsigsegv on Panther will take care of most of the build issues.

-Greg

[yaseppochi (Stephen J. Turnbull)]

(In reply to comment #4)

I have just committed a portfile for clisp 2.37. The default is now to build without dynamic foreign function support, and to not use libsigsegv on Panther (10.3.x).

Thanks!

Unfortunately, port doesn't want to listen to you:

papa% port clean clisp ---> Cleaning clisp papa% port uninstall libsigsegv ---> Deactivating libsigsegv 2.1_0 ---> Uninstalling libsigsegv 2.1_0 papa% port upgrade clisp ---> Unpacking tgz archive for libsigsegv 2.1_0 ---> Installing libsigsegv 2.1_0 ---> Activating libsigsegv 2.1_0 Error: Target com.apple.activate returned: Image error: /opt/local/include/sigsegv.h already exists and does not belong to a registered port. Unable to activate port libsigsegv. ---> Fetching clisp

and of course clisp blows chunks. Maybe if we hit it with a 2x4:

papa% port clean clisp ---> Cleaning clisp papa% port uninstall libsigsegv ---> Uninstalling libsigsegv 2.1_0 papa% rm /opt/local/include/sigsegv.h papa% port uninstall clisp ---> Deactivating clisp 2.35_1 ---> Uninstalling clisp 2.35_1 papa% port install clisp +nolibsigsegv ---> Fetching clisp ---> Verifying checksum(s) for clisp ---> Extracting clisp ---> Applying patches to clisp ---> Configuring clisp ---> Building clisp with target all ---> Staging clisp into destroot ---> Packaging tgz archive for clisp 2.37_0+darwin_7+nolibsigsegv ---> Installing clisp 2.37_0+darwin_7+nolibsigsegv ---> Activating clisp 2.37_0+darwin_7+nolibsigsegv ---> Cleaning clisp papa%

It looks like it's "port uninstall clisp" that did the trick, I'm reinstalling without +nolibsigsegv now. port didn't try to install libsigsegv this time, but I'm going to bed now. If the build fails, I'll let you know, otherwise you can assume that not only do 10.3.x users have to uninstall libsigsegv, but they also should port uninstall clisp.

[yaseppochi (Stephen J. Turnbull)]

(In reply to comment #5)

If the build fails, I'll let you know, otherwise you can assume that not only do 10.3.x users have to uninstall libsigsegv, but they also should port uninstall clisp.

Built and installed OK, looks like 10.3.x users need to do "port uninstall libsigsegv clisp", then "port install clisp".

[gwright@…]

Hi Stephen,

Thanks for testing. The procedure should be as you stated, uninstall both clisp and libsigsegv, then just installing clisp. The problem you noticed with "port upgrade" is a bug in the darwinport infrastructure, which ignores platform and variant information, always building the default configuration on upgrade.

(Yes, that also means that if the upgrade bug doesn't get tracked down before the next clisp release, it will be necessary to uninstall and reinstall instead of using "port upgrade.)

I will mark this bug as closed, and add you observations to the upgrade bug report. Thanks!

Best Wishes, Greg

[gwright@…]

Hi Stephen,

Thanks for testing. The procedure should be as you stated, uninstall both clisp and libsigsegv, then just installing clisp. The problem you noticed with "port upgrade" is a bug in the darwinport infrastructure, which ignores platform and variant information, always building the default configuration on upgrade.

(Yes, that also means that if the upgrade bug doesn't get tracked down before the next clisp release, it will be necessary to uninstall and reinstall instead of using "port upgrade.)

I will mark this bug as closed, and add you observations to the upgrade bug report. Thanks!

Best Wishes, Greg

[yaseppochi (Stephen J. Turnbull)]

Regression in 2.38_1.

[yaseppochi (Stephen J. Turnbull)]

Oops ... forgot that this was considered a DarwinPorts bug.

Sorry for the noise.