Opened 14 years ago

Closed 13 years ago

#25496 closed defect (duplicate)

clisp: dyld: Library not loaded: /opt/local/lib/libsigsegv.2.dylib

Reported by: jwiegley@… Owned by: waqar@…
Priority: Normal Milestone:
Component: ports Version: 1.9.1
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: clisp

Description

When I try to build clisp, it complains that libsigsegv is not installed. I installed that, still complained. I installed it again with +universal, it still complained.

So I installed it with +nolibsigsegv. It built successfully, but when I run it it crashes because it can't find libsigsegv!!

vulcan ~/Contracts/TI $ sudo port install clisp +nolibsigsegv
--->  Computing dependencies for clisp
--->  Fetching archive for clisp
--->  Fetching clisp
--->  Verifying checksum(s) for clisp
--->  Extracting clisp
--->  Configuring clisp
--->  Building clisp
--->  Staging clisp into destroot
--->  Packaging tbz2 archive for clisp 2.48_0+nolibsigsegv
--->  Installing clisp @2.48_0+nolibsigsegv
--->  Activating clisp @2.48_0+nolibsigsegv
--->  Cleaning clisp
vulcan ~/Contracts/TI $ clisp
dyld: Library not loaded: /opt/local/lib/libsigsegv.2.dylib
  Referenced from: /opt/local/lib/clisp-2.48/base/lisp.run
  Reason: image not found
zsh: trace trap  clisp

Change History (7)

comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added; waqar@… removed
Owner: changed from macports-tickets@… to waqar@…
Summary: Can't get clisp to build on 10.6clisp: dyld: Library not loaded: /opt/local/lib/libsigsegv.2.dylib

Does the file /opt/local/lib/libsigsegv.2.dylib exist? Is it a valid library and built for the right architectures? (What does "lipo -info /opt/local/lib/libsigsegv.2.dylib" say?)

comment:2 in reply to:  description Changed 14 years ago by tom.winans@…

I issued "sudo port install clisp +nolibsigsegv -f" on OSX 10.6.2 and was successfully able to invoke clisp 2.48 from the command line. I did ensure that /opt/local/lib contained no "libsigsegv" cruft, which appeared to remain after port cleans. You might try this.

comment:3 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Of course "sudo port clean" would not remove anything from /opt/local/lib; that is not its function. "sudo port deactivate libsigsegv" or "sudo port uninstall libsigsegv", on the other hand, should remove all parts of libsigsegv if it was MacPorts that originally installed it.

comment:4 in reply to:  1 ; Changed 14 years ago by jwiegley@…

Replying to ryandesign@…:

Does the file /opt/local/lib/libsigsegv.2.dylib exist? Is it a valid library and built for the right architectures? (What does "lipo -info /opt/local/lib/libsigsegv.2.dylib" say?)

It does not exist.

comment:5 in reply to:  4 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

I just noticed a change in MacPorts 1.9 caused a problem for the clisp port on Snow Leopard, which I've fixed in r69483. Please see if clisp @2.48_1 fixes the problem.

comment:6 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Actually, that might not help; I think you're seeing #25580.

comment:7 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: duplicate
Status: newclosed
Note: See TracTickets for help on using tickets.