public inbox for
help / color / mirror / Atom feed
From: marco atzeri <>
Subject: Re: Missing X11 Libraries
Date: Tue, 11 Jun 2013 05:03:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Il 6/11/2013 6:46 AM, Dan Piraner ha scritto:
> Dear all,
> I am a new Cygwin user trying to utilize the environment for running
> AmberTools 13 from I followed their instructions for
> configuring the installation and upon running the configure script, I
> got a message saying that my XHOME directory could not be determined.
> Upon some online investigation I learned that Xhome is supposed to be
> the directory containing "lib/libXt.a", and that this directory is
> searched for in /usr/X11R6/lib. However, my /usr/X11R6 directory does
> not contain a "lib" subdirectory; it only contains "bin" and "share".

/usr/X11R6/lib is obsolete, looks on /usr/lib

libXt.a is a static library, on cygwin we have only the dynamic version


that belongs to libXt-devel-1.1.4-1 package

> I'm pretty sure that I have all required components installed;
> setup.exe shows almost everything in the X11 section set to "keep". In
> particular, the AMBER installation guide calls for the following X11
> packages, all of which are set to "keep":
> libXt-devel
> xinit
> xorg-scripts
> xorg-server-devel
> Could someone please advise me as to how to obtain the X11R6/lib
> directory and its associated contents?
> Thank you,
> Dan
> P.S. I tried to paste my CygCheck.out contents here but the email
> bounced with a message saying it exceeded the maximum size. Please let
> me know if there are any particular subsections that I should send.

strange ow long is it ?

Unsubscribe info:
Problem reports:

  reply	other threads:[~2013-06-11  5:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11  4:46 Dan Piraner
2013-06-11  5:03 ` marco atzeri [this message]
2013-06-11 18:49 ` Larry Hall (Cygwin-X)
2013-06-11 18:49 ` Csaba Raduly
2013-06-11 19:47   ` Dan Piraner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).