public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool
Date: Thu, 17 Nov 2011 20:34:00 -0000	[thread overview]
Message-ID: <4EC56FB1.4000007@gmail.com> (raw)
In-Reply-To: <4EC50550.7020403@gmail.com>

On 17/11/2011 13:00, marco atzeri wrote:

> the problem is that the configure scripts incorrectly looks for
> libpcre.so that on cygwin is called differently:
> 
> /usr/bin/cygpcre-0.dll
> 
> so you need to modify the configure accordingly or
> remove the test and leave only the check for "pcre.h"
> 
> same for libidn     /usr/bin/cygidn-11.dll
> 
> libpq     /usr/bin/cygpq.dll
> 
> and so on.
> These are upstream bugs in configure, looking for the lib
> is wrong as different platforms have different conventions.
> They should only look for the header.

  Well, they could look for the lib too, as long as they used the correct
autoconf macro (AC_CHECK_LIB or AC_SEARCH_LIB) to do so.  Rather than try
searching in arbitrary and unknown places for unknown file names, that just
tries running a compile with the relevant -l flag and seeing if it succeeds -
which for the purposes of the build is more definitively accurate anyway.


    cheers,
      DaveK


--
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

  reply	other threads:[~2011-11-17 20:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 19:28 viper_88
2011-11-15 20:46 ` Larry Hall (Cygwin)
2011-11-16 19:34   ` viper_88
2011-11-16 20:01     ` marco atzeri
2011-11-17 12:15       ` viper_88
2011-11-17 13:00         ` marco atzeri
2011-11-17 20:34           ` Dave Korn [this message]
2011-11-17 20:38             ` Dave Korn
2011-11-17 18:50         ` Andrey Repin
2011-11-16 20:05     ` Jesse Ziser
2011-11-16 20:41       ` Tim Prince
2011-11-16 20:12     ` Christopher Faylor

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=4EC56FB1.4000007@gmail.com \
    --to=dave.korn.cygwin@gmail.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).