Opened 17 years ago
Closed 14 years ago
#14018 closed defect (duplicate)
cssh fails lo load (Bus error)
Reported by: | andrelop@… | Owned by: | stechert@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | jonathan@…, lists@…, straxus@… | |
Port: | cssh |
Description
After jumping through many hoops to get it compiled (see ticket #14016), when trying to run cssh I get the following error :
white:~ andrelop$ cssh -l root@192.168.10.251 Bus error white:~ andrelop$
I'm using a MacOSX 10.5.1 (Leopard) fully updated as of some minutes ago and using MacPorts 1.600.
Change History (21)
comment:1 Changed 17 years ago by andrelop@…
comment:2 Changed 17 years ago by afb@…
Seems to work OK on Tiger, so could be yet another Leopard X11 bug ?
comment:3 Changed 17 years ago by jmroot (Joshua Root)
Cc: | andrelop@… removed |
---|---|
Owner: | changed from macports-tickets@… to stechert@… |
Assigning to maintainer.
comment:4 Changed 17 years ago by stechert@…
Status: | new → assigned |
---|
comment:5 Changed 17 years ago by stechert@…
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I updated to v3.22 of cssh. Have verified that I can run cssh on my Leopard box version 10.5.2 with MacPorts 1.600.
comment:7 Changed 16 years ago by jonathan@…
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Version 3.22 still gives a Bus Error for me, with latest Leopard updates (10.5.2) and Macports 1.600.
According to http://www.nabble.com/ClusterSSH---Leopard-Fix-td14848155.html the cause is Macports Tk:
$ /opt/local/bin/perl -e 'use Tk;' Bus error
So, this is not resolved until Tk is fixed in Macports.
comment:10 Changed 16 years ago by raimue (Rainer Müller)
Upstream bug report: http://rt.cpan.org/Public/Bug/Display.html?id=39593
comment:13 Changed 15 years ago by tobypeterson
Port: | cssh added |
---|---|
Version: | 1.6.0 |
comment:14 Changed 15 years ago by blb@…
For anyone with this issue, how is your perl5.8 port installed? port installed perl5.8
comment:15 Changed 15 years ago by straxus@…
#:~ $ cssh Bus error #:~ $ which perl /opt/local/bin/perl #:~ $ port installed perl5.8 The following ports are currently installed:
perl5.8 @5.8.9_2 (active)
comment:17 Changed 15 years ago by blb@…
I have a theory that using a perl5.8 without +shared may be the/a cause to these odd bus errors some people are experiencing. straxus, if you don't mind, could you try updating your perl5.8 port by running
sudo port -fn upgrade perl5.8 +shared
Then try cssh again.
comment:18 Changed 15 years ago by straxus@…
#:~ $ sudo port -fn upgrade perl5.8 +shared ---> Fetching perl5.8 ---> Verifying checksum(s) for perl5.8 ---> Extracting perl5.8 ---> Configuring perl5.8 ---> Building perl5.8 ---> Staging perl5.8 into destroot ---> Unable to uninstall perl5.8 5.8.9_2, the following ports depend on it: ---> perl5 Warning: Uninstall forced. Proceeding despite dependencies. ---> Deactivating perl5.8 @5.8.9_2 ---> Uninstalling perl5.8 @5.8.9_2 ---> Installing perl5.8 @5.8.9_2+shared ---> Activating perl5.8 @5.8.9_2+shared ---> Cleaning perl5.8 #:~ $ cssh Bus error #:~ $ port installed perl5.8 The following ports are currently installed: perl5.8 @5.8.9_2+shared (active)
comment:19 follow-up: 20 Changed 15 years ago by blb@…
Hmm, could be a need to rebuild p5-tk as well. However, if you do get past the bus error here, cssh still won't work if you're on 10.5 as p5-x11-protocol doesn't currently work with the launchd setup of X11 (see the bug for X11::Protocol).
You may want to try the newly-added csshX port if you don't need it running in X11 (csshX is Terminal.app-based).
comment:20 Changed 15 years ago by straxus@…
Thanks, csshX worked perfectly for me! I think the bug remains open though, with csshX as a workaround for now - it'd be nice to get cssh working (as well as anything else relying upon Perl 5's X11 support).
comment:21 Changed 14 years ago by jmroot (Joshua Root)
Resolution: | → duplicate |
---|---|
Status: | reopened → closed |
So I guess this is a dupe of #18391.
More info. The only thing I got from googling fot this error is http://www.mail-archive.com/macports-users@lists.macosforge.org/msg05921.html, which unfortunately doesn't have any solution or proposed patch.