Hi Stefan,
Thanks a lot for you help so far. Unfortunately,
the commands you give seem not work for me.
Possibly, I have overlooked something.
First, a question: if I do
sudo port -v extract xfig
I get no message or whatsoever, just a new prompt; is that OK?
Then, I try:
cd `port dir xfig`/work/xfig.3.2.5/
but this fails, there is no such directory:
`port dir xfig` expands to
/opt/local/var/macports/sources/rsync.macports.org/release/ports/
graphics/xfig
and in there there is an empty dir "work"
(to be precise there is one empty file ".macports.xfig.state"),
so no dir xfig.3.2.5.
Do you know what to try next?
Thanks again,
Dimitri
On 24 Jul 2007, at 05:04, Stefan Bruda wrote:
There does not seem to be possible to use the portfile for this
purpose,
though a patch could be written and applied by the portfile. Being
lazy
and lacking time, what I did instead is:
port -v extract xfig
cd `port dir xfig`/work/xfig.3.2.5/
vi Imakefile
# search for: #define XAW3D
# comment (XCOMM) the just found line
port -v install xfig
I also edited the port:
vi `port file xfig`
and I eliminated the dependency of port:Xaw3d. This is not
theoretically
necessary but is correct given that I just eliminated the actual Xaw3d
dependency.
BY the way, did anybody notice that upgrading Xaw3d to 1.5E_1
breaks quite
badly other things such as xemacs and gv? Any suggestions on what
could
be done about this one?
This sounds like a matter for the maintainer of the xfig port, whom
I'm Cc'ing on this email.
I believe that Xaw3D is the overall culprit, so the dependency
should be
removed (and the Imakefile patched accordingly) until the issue is
fixed.
Cheers,
Stefan
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
