From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: aplus-fsf (XWarpPointer)
Date: Wed, 21 Mar 2012 19:54:00 -0000 [thread overview]
Message-ID: <4F6A31F0.8090500@cygwin.com> (raw)
In-Reply-To: <CABn7SNboxAf5bjL0qrAOnE0gfGOmKuiCASK4S=t7NW2Df7hHcg@mail.gmail.com>
On 3/21/2012 1:39 PM, Tom Szczesny wrote:
> a snippet from aplus-fsf-4.22/src/main/Makefile :
<snip>
> I assume that the line
> X_LIBS= -L -lX11
> should read something different.
Indeed.
> I've tried various things to no avail.
> What is normally put in a Makefile to indicate the location of X_LIBS
> for a Cygwin build?
In this case, the culprit is a buggy (or bit-rotted?) configure script for
Cygwin. A library search path is not set up so, well, the script ends
up with an empty one. As a result, there's no path to put after the
-L flag. Since libX11.dll.a is in /usr/lib, you should be able to get away
with just eliminating the -L flag completely from the Makefile (I didn't
test this).
In general, the best place for X specific questions with Cygwin is the
cygwin-xfree list though. That's where the most knowledgeable X folks
are.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-03-21 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 17:39 Tom Szczesny
2012-03-21 19:54 ` Larry Hall (Cygwin) [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-21 13:08 Tom Szczesny
2012-03-21 13:29 ` Michel Bardiaux
2012-03-21 12:09 Tom Szczesny
2012-03-21 12:47 ` Michel Bardiaux
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F6A31F0.8090500@cygwin.com \
--to=reply-to-list-only-lh@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).