I googled on the subject problem and found some rather obscure recommendations, mostly in previous conversations in this list. I could not find a previous reference to what I believe is a satisfactory workaround:
Edit /scid/configure and include "/usr/share/doc/libx11-dev" in x11Path (around line 210). This directory, which is part of the Ubuntu minimal package, happens to contain a subdirectory named libX11, (So far as I know, this subdirectory is the only one on an Ubuntu minimal system that is so-named). While the libX11 subdirectory in question contains only documentation, >>no headers and no source code<<, it appears to satisfy the configure script. After this, unaccountably, scid compiles and installs without difficulty. I have not tested, but this would also seem to imply that creating an empty directory named libX11 in, say, /usr/lib/ will have the same effect. Why configure insists on finding a directory of which it makes no subsequent use is an interesting question. Maybe there is a more general test for making sure X is available on any given system? At any rate, this workaround allowed me to install scid, where the configure script before choked and prevented installation. Best to all. ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
