Hi Ryan,

Sorry, I hadn't seen the second paragraph in your first email.  To
answer your questions, I originally installed MacPorts from a disk
image, onto an iMac, running Mac OS 10.4 (Tiger).  I am still on Tiger,
though I did (apparently, successfully) do a `sudo port selfupdate' and
`sudo port upgrade outdated'.  Running `sudo port clean xorg-libX11'
appears to have fixed it, however, because after doing that I was able
to install plplot without a problem.

Thanks much, for the suggestion to run port clean.  

Best,
David  

On Wed, 2009-10-14 at 08:16 -0500, Ryan Schmidt wrote:
> On Oct 14, 2009, at 08:06, David A. Ventimiglia wrote:
> 
> > Ryan Schmidt wrote:
> >
> >> I'm not sure how you got in this situation. How did you initially
> >> install MacPorts? On what machine, with what version of Mac OS X,
> >> Xcode and MacPorts? Are you still on those versions or have you
> >> upgraded (to what)? Have you run "sudo port selfupdate" to make sure
> >> you have the latest MacPorts and port definitions? If you still
> >> experience the issue, can you please clean the affected port ("sudo
> >> port clean xorg-libX11") and then try again with the debug switch
> >> ("sudo port -d install xorg-libX11") and send us all the output so we
> >> can try to figure out what's going wrong?
> 
> 
> > still get this error when I try `sudo port install plplot', and I  
> > found
> > nothing on the Wiki referring to this.  If the error I'm getting is
> > unfamiliar to anyone, ok, that's fine, I'll figure it out.  But I was
> > hoping someone would say, "oh, the 'libX11 no such directory'  
> > problem, I
> > know how to fix that."
> 
> I haven't heard it mentioned before. First step would be to clean and  
> try again. If it fails again and you need help, please show us the  
> debug output.
> 
> 
> 
> 
-- 
David A. Ventimiglia <[email protected]>
Michigan State University

_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Reply via email to