public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Please add 'AVG Internet Security 2011' to the BLODA list (and cygport also :-) ).
Date: Mon, 07 Feb 2011 15:45:00 -0000	[thread overview]
Message-ID: <4D50138B.5020001@redhat.com> (raw)
In-Reply-To: <4D4F77BE.4000305@serv.net>

[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]

On 02/06/2011 09:40 PM, L Anderson wrote:
> In regards to the aforementioned while loop in 'conftest.c'--the logic
> of it being run for every invocation of a 'coreutils' build escapes me.
> I can see running it once per OS, outside of the build process, to
> determine if the given OS does the right thing; after that, shouldn't it
> just be a case of checking if the OS being used has been tested and
> deemed to behave properly?

Yes, this particular configure test takes a long time, even without
virus scanning, on WinXP (where Microsoft has an O(n^2) implementation);
it's faster on newer Windows (where Microsoft fixed things to be O(n)).

You can pre-seed a config.site cache to skip the test by using a known
outcome result (in fact, I do just that when building coreutils):

$ cat >> /usr/config.site <<\EOF
# configure gets the right answer, but only after hammering the system
gl_cv_func_getcwd_path_max=yes
EOF

I suppose I should also tweak my coreutils*.cygport file to pre-seed the
cache at configure time (by adding gl_cv_func_getcwd_path_max=yes to
CYGCONF_ARGS), but that won't help you when upgrading to
coreutils-8.10-1.cygport, which came out between your report against 8.8
and this email.

-- 
Eric Blake   eblake@redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  parent reply	other threads:[~2011-02-07 15:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07  4:40 L Anderson
2011-02-07  5:48 ` David Arnstein
2011-02-07  9:16 ` Vincent Rivière
2011-02-07 16:37   ` L Anderson
2011-02-07 15:45 ` Eric Blake [this message]
2011-02-15  5:13   ` L Anderson
2011-02-15 15:17     ` Eric Blake

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=4D50138B.5020001@redhat.com \
    --to=eblake@redhat.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).