public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: setup.exe 2.573.2.3 signature failure
Date: Fri, 16 Jan 2009 16:30:00 -0000	[thread overview]
Message-ID: <4970A862.4070505@cygwin.com> (raw)
In-Reply-To: <f7c6d5f90901152033u6b694b7fhcbb19d30037d4865@mail.gmail.com>

George R Nelson wrote:
> As a newcomer to cygwin, my attempts to download from ctgwin.com or a
> number of mirror sites all failed with signature errors. WHy do I get
> this problem? The error I get is:
> 
> Setup.ini signature http://cygwin.com/setup.bz2.sig from
> http//cygwin.com failed to verify.
> 
> I have managed to download cygwin using the setup.exe from redhat.

So what were you downloading it with before?  'setup.exe' is the
prescribed way to download (for installation) and/or install.  If you
want a mirror, you want to use another tool but barring that,
stick with 'setup.exe'.

> On a related topic, is there any way to change the URL for the
> download? Or do you just add download sites then highlight the one you
> wish to use?

There are plenty of download sites in the list to choose from.  But if
you want another one not listed, you can add it by typing it into the
edit control below the list and clicking "Add".  Then you can select it
from the list.  You can select up to 4 from the list.

> Finally, I am trying to build some C sources using cygwin but the
> build fails as it is not finding some libraries: libsocket.a, libnsl.a
> and libxnet.a. I've searched both the package lists and the installed
> libraries without success. I am sure that the functions defined in
> these libraries do exist in the cygwin distribution but may be in
> differently named libraries. Can anybody help?

Not significantly with that description.  I'd recommend reading the
problem reporting guidelines and trying again if you're still having
problems.  The guidelines can be found at the link below.

> Problem reports:       http://cygwin.com/problems.html



-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

  reply	other threads:[~2009-01-16 15:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16  8:13 George R Nelson
2009-01-16 16:30 ` Larry Hall (Cygwin) [this message]
2009-01-16 20:24   ` George R Nelson
2009-01-16 21:49     ` Larry Hall (Cygwin)
2009-01-16 21:54       ` Larry Hall (Cygwin)
2009-01-17  5:55       ` George R Nelson
2009-01-17  8:13         ` Larry Hall (Cygwin)
2009-01-17 10:46 ` Dave Korn

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=4970A862.4070505@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.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).