public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Larry Hall (Cygwin-X)" <reply-to-list-only-lh@cygwin.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Linking Errors related to X11
Date: Wed, 21 Mar 2012 23:05:00 -0000	[thread overview]
Message-ID: <4F6A5E96.60706@cygwin.com> (raw)
In-Reply-To: <CABn7SNZN7_apdXkDLsbF7E4T_dzU9HgTAcikUk9sF4Yr05F+zQ@mail.gmail.com>

On 3/21/2012 6:19 PM, Tom Szczesny wrote:
> I am attempting to port the aplus-fsf-4.22 package (available at
> www.aplusdev.org) to cygwin,
> and I'm getting linking errors related to X11.
>
> I can build the package successfully on Gentoo Linux.
>
> The build on cygwin fails at   /aplus-fsf-4.22/src/main/aplus-main.c
> with many error messages related to X11, such as
>      undefined reference to '_XWarpPointer'.
>
> The Makefile.in contains the lines:
>     X_INCLUDES = @X_INCLUDES@
>     X_LIBS = @X_LIBS@
>
> which got translated (in the Makefile) to:
>     X_INCLUDES = -I
>     X_LIBS = -L -lX11
>
> While this works when building in Gentoo Linux, it does not appear to
> be correct for cygwin.
> What is the correct specification when building the package in cygwin?

Try these:

X_INCLUDES = /usr/include
X_LIBS = -L /usr/include -lX11

You can also override the faulty configure script values and point
directly at these paths with the -x-includes and -x-libraries
flags.

I didn't test these settings so you may need to experiment a little.
But essentially you can find the paths you're looking for by checking
out the contents on the libX11-devel package, which you should
already have.




-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2012-03-21 23:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 22:19 Tom Szczesny
2012-03-21 23:05 ` Larry Hall (Cygwin-X) [this message]
2012-03-22 14:34   ` Christopher Faylor
2012-03-22 14:38     ` Larry Hall (Cygwin-X)
2012-03-22 17:55 ` Tom Szczesny
2012-03-22 18:23   ` Jack
2012-03-22 19:23   ` Christopher Faylor
2012-03-22 19:52     ` Yaakov (Cygwin/X)
2012-03-22 19:47 Tom Szczesny
2012-03-22 19:52 ` Larry Hall (Cygwin-X)
2012-03-22 20:22 ` Tom Szczesny
2012-03-22 22:37   ` Yaakov (Cygwin/X)
2012-03-22 22:41 ` Yaakov (Cygwin/X)
2012-03-22 20:31 Tom Szczesny
2012-03-22 20:55 Tom Szczesny
2012-03-22 21:08 ` Larry Hall (Cygwin-X)
2012-03-23  1:51 Tom Szczesny

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=4F6A5E96.60706@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --cc=cygwin-xfree@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).