Opened 13 years ago
Closed 13 years ago
#30706 closed defect (fixed)
gnome-utils: baobab won't run, complains about Darwin version
Reported by: | Russell-Jones-OxPhys (Russell Jones) | Owned by: | dbevans (David B. Evans) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.1 |
Keywords: | Cc: | ||
Port: | gnome-utils |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Steps to reproduce
- Start terminal
- run baobab
Actual result
$ baobab Can only run on Darwin 10.7.0 i386 glibtop: read 8 bytes: Resource temporarily unavailable $
Note glibtop rather than libgtop
Expected result
baobab runs
Am presently running selfupdate, but no relevant packages seem affected: atlas py27-cython texlive-basic wine-devel
Change History (5)
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | devans@… removed |
---|---|
Description: | modified (diff) |
Owner: | changed from macports-tickets@… to devans@… |
Summary: | Baobab won't run, complains about Darwin version → gnome-utils: baobab won't run, complains about Darwin version |
comment:2 Changed 13 years ago by Russell-Jones-OxPhys (Russell Jones)
10.8.0. But I've never run anything else on the machine concerned (Or are Darwin versions not fixed for each OS X version?) I'm trying port upgrade --force gnome-utils now.
Thanks, Russell
comment:3 Changed 13 years ago by jmroot (Joshua Root)
OS X 10.6.7 was Darwin 10.7.0. But there shouldn't be any reason why something built on Darwin 10.x shouldn't run on 10.y where y >= x.
comment:4 Changed 13 years ago by Russell-Jones-OxPhys (Russell Jones)
It took a long time, but did indeed fix the problem. Thanks. So I guess 10.5.x was Darwin 9.x ? No need to answer unless you'd like to, I should look it up on Wikipedia :)
comment:5 Changed 13 years ago by dbevans (David B. Evans)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Traced this error to libgtop. Rebuilding that port fixed the problem for me. libgtop updated to version 2.28.4 in r84087.
And what Darwin version are you running now? If it is different from the above, consider rebuilding the port.