public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@gmail.com>
To: "The Are-They-Trolling-Us? And Vulgar Cygwin-Talk Maiming List"
	<cygwin-talk@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:51:00 -0000	[thread overview]
Message-ID: <4EC5739F.3000600@gmail.com> (raw)
In-Reply-To: <4EC570BC.2010202@gmail.com>

On 17/11/2011 20:38, Dave Korn wrote:
> On 17/11/2011 20:33, Dave Korn wrote:
>> On 17/11/2011 13:00, marco atzeri wrote:

>>> 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.  
> 
> 
>   Whoops, no they can't.  The hydra configure script isn't from autconf at
> all; it's just hand-written.

  Good grief.  It also has a Makefile.am and a Makefile.in, but it doesn't use
automake, and their contents are unrelated.  It just cats them together into
the final makefile!

    cheers,
      DaveK



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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <32849825.post@talk.nabble.com>
     [not found] ` <4EC2CFA2.40007@cygwin.com>
     [not found]   ` <32857072.post@talk.nabble.com>
     [not found]     ` <4EC41689.8090601@gmail.com>
     [not found]       ` <32861517.post@talk.nabble.com>
     [not found]         ` <4EC50550.7020403@gmail.com>
     [not found]           ` <4EC56FB1.4000007@gmail.com>
     [not found]             ` <4EC570BC.2010202@gmail.com>
2011-11-17 20:51               ` Dave Korn [this message]
2011-11-17 21:07                 ` Eric Blake
2011-11-17 21:32                   ` Christopher Faylor
2011-11-17 22:34                     ` JonY
2011-11-17 23:46                   ` Charles Wilson

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=4EC5739F.3000600@gmail.com \
    --to=dave.korn.cygwin@gmail.com \
    --cc=cygwin-talk@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).