> checking X11/Intrinsic.h usability... yes > checking X11/Intrinsic.h presence... yes > checking for X11/Intrinsic.h... yes > checking for XtToolkitInitialize in -lXt... no > configure: error: --with-x=yes (default) and X11 headers/libs are not > available > > Any suggestions would be great. My main point is that you can compile R > in leopard without X support, and get something that seems fully > functional through the GUI and is capable of building packages again.
It would probably be a good idea for someone with a leopard box (I don't have one yet, sorry...) to go through the configure script, figure out why the XtToolkitInitialize test is failing, and report that back to the list (along with the location of the sought file on Leopard, if it exists...). It is likely that the configure test just isn't smart enough to deal with a file location change, or something, on leopard. [I run into this stuff all the time building Solaris apps.... a lot of configure scripts are just plain awful.] --elijah _______________________________________________ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
