public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Tom Szczesny <tavmem@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Linking Errors related to X11
Date: Fri, 23 Mar 2012 01:51:00 -0000 [thread overview]
Message-ID: <CABn7SNaCxsXLztfQ2zvguddXuXZ4sWwDBGk=7pYeVFUQOpy=Xg@mail.gmail.com> (raw)
Yaakov wrote:
"For future reference, this package includes a very old version of libtool
which is not guaranteed to work on Cygwin. This is why running autoreconf
is standard procedure when building autoconf-based packages."
Thank you for this comment. It gives me a place to start.
If there are any other important initial steps to the "standard procedure",
(or a place to find a list of all the steps) please let me know.
Also: The issues that I am facing are clearly not specific to the
cygwin-xfree group. When I do have further questions related to porting
a very old package (that does still build and work on Linux) to cygwin,
which is the best forum in which to ask them?
--
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/
next reply other threads:[~2012-03-23 1:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 1:51 Tom Szczesny [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-22 20:55 Tom Szczesny
2012-03-22 21:08 ` Larry Hall (Cygwin-X)
2012-03-22 20:31 Tom Szczesny
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-21 22:19 Tom Szczesny
2012-03-21 23:05 ` Larry Hall (Cygwin-X)
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)
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='CABn7SNaCxsXLztfQ2zvguddXuXZ4sWwDBGk=7pYeVFUQOpy=Xg@mail.gmail.com' \
--to=tavmem@gmail.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).