Opened 15 years ago
Closed 14 years ago
#20644 closed defect (invalid)
OSX 10.4.11, ppc, xfig gets bus error on startup, may be X11 configuration error
| Reported by: | davidh@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.7.1 |
| Keywords: | x11 | Cc: | |
| Port: | xfig |
Description
I've just installed xfig, and I get a list of missing resources followed by a bus error on startup.
I suspect things will go much better with the resources, but how do I set them up?
See the attached x11 app session for what's going on.
Attachments (3)
Change History (13)
Changed 15 years ago by davidh@…
| Attachment: | xfig_bug.txt added |
|---|
comment:1 follow-up: 2 Changed 15 years ago by tobypeterson
Please attach the crash log. Also, what version of Xcode are you using?
Changed 15 years ago by davidh@…
| Attachment: | xorg_portlist.txt added |
|---|
file from the shell command: port list installed | grep xorg >xorg_portlist.txt
comment:2 follow-up: 3 Changed 15 years ago by davidh@…
Replying to toby@…:
Please attach the crash log. Also, what version of Xcode are you using?
XCode 2.4.1, last modified Nov 5 2007
comment:3 Changed 15 years ago by davidh@…
comment:4 follow-up: 5 Changed 15 years ago by tobypeterson
Ok, old version of Xcode may be at fault. Also, you still haven't attached the crash log.
comment:5 Changed 15 years ago by davidh@…
Replying to toby@…:
Ok, old version of Xcode may be at fault. Also, you still haven't attached the crash log.
What do you mean crash log? I thought the terminal session was the log you meant.
Do you mean a core file? Where?
Changed 15 years ago by davidh@…
| Attachment: | xfig.crash.log added |
|---|
crash log from very first xfig crash
comment:7 Changed 15 years ago by jmroot (Joshua Root)
Lots of libs from /usr/X11R6 being used there. Are your ports up to date?
comment:8 Changed 15 years ago by davidh@…
please close this bug report.
I had moved /opt/local to another drive, then planted a symbolic link "opt" on the boot drive.
What happened is that the X11 files libraries loaded with the executable were osx X11, not the xorg installation with macports once the dylib files moved.
I have since fixed this by setting the DYLD_LIBRARY_PATH variable to point to the new location of /opt/local/lib.
This might be worth a hint in the documentation. Its not nice to mess with mother nature, but if you must... here is a hint.
comment:9 Changed 15 years ago by blb@…
You shouldn't need to be setting any DYLD environment variables to get things to work, including with a symlink assuming things like /opt/local/lib/libX11.6.dylib still work.
comment:10 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
terminal session