I have previously gotten starlink to build on a 32bit dapper drake
install, and I'm now trying it on a 64bit install with a fresh checkout
from the cvs. This time I'm keeping notes of the problems I've run into!
Currently I'm stuck on an apparently failed X11 dependency in gwm:
configure: error: No X11 development system found. Cannot continue
configure: error: /bin/sh './configure' failed for gwm
configure: error: /bin/sh './configure' failed for libraries
I looked at configure.ac for gwm and see that the message is caused by
AC_PATH_XTRA
I've been looking at the definition of this macro to see what it does:
thirdparty/fsf/autoconf/lib/autoconf/libs.m4
and found the place where it fails. If you follow through AC_PATH_XTRA
(via AC_PATH_X) you get to:
_AC_PATH_X_XMKMF
Here ac_x_includes gets set to "no" and ac_x_libraries set to
"/usr/X11R6/lib", hence the failure. Inside the includes check it looks
for $ac_im_incroot/X11/Xos.h which sure enough doesn't exist
(ac_im_incroot is /usr/X11R6/include) - the /include directory doesn't
exist there. However, I do have a /usr/include/X11/Xos.h
Inside the gwm directory if I instead do
./configure --x-includes=/usr/include/X11 --x-libraries=/usr/lib/X11/
it seems to work to completion. I then decided to go back to the top of my
starlink build tree and attempt a new configure -C before doing make
world, using the same configure options. When it gets down to gwm it borks
on the same X11 dependency - should options passed to the top-level
configure script get passed to the children?
For reference, I've installed X development files with the following
packages:
sudo apt-get install libx11-dev
Once I get the whole thing building I will post detailed instructions.
cheers,
Ed
|