From: David Rothenberger <daveroth@acm.org>
To: cygwin@cygwin.com
Subject: Re: libapr1 in cygwin
Date: Sun, 18 Jan 2009 22:12:00 -0000 [thread overview]
Message-ID: <4973A0FD.9060108@acm.org> (raw)
In-Reply-To: <27dfa3d0901181326n3fa7b587k918b82b85af766f8@mail.gmail.com>
On 1/18/2009 1:26 PM, Daniel Stonier wrote:
> David Rothenberger wrote:
>> I recall that the build failed when static libraries were enabled.
[snip]
> However, I've run into a few hitches with the cygwin source build - I
> just started using cygwin yesterday, so not very familiar with its
> build system/environment and got thrown by errors coming from a
> libtool mismatch. I'll keep at it - I think we're going to need cygwin
> to build our user end programs so I'll need to familiarise myself with
> it regardless.
In case you missed it, I just packaged a new version with static
libraries. The problem was the build/libtool.m4 file in the source
tarball conflicted with the version of libtool now used in the Cygwin
distribution. Removing that file before building solves the problem.
Contact me off-list if you can't wait for the new packages to be
uploaded -- I can provide you with a pointer to them or the updated
cygport files for you to build it yourself.
--
David Rothenberger ---- daveroth@acm.org
Friends, n.:
People who borrow your books and set wet glasses on them.
People who know you well, but like you anyway.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
prev parent reply other threads:[~2009-01-18 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <27dfa3d0901180829w49c2157cl2c3249be2132c33e@mail.gmail.com>
2009-01-18 20:55 ` David Rothenberger
2009-01-18 21:09 ` David Rothenberger
2009-01-18 21:44 ` Daniel Stonier
2009-01-18 22:12 ` David Rothenberger [this message]
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=4973A0FD.9060108@acm.org \
--to=daveroth@acm.org \
--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).