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: mkpasswd (434): [31] A device attached to the system is not functioning.
Date: Sun, 08 Aug 2010 23:51:00 -0000	[thread overview]
Message-ID: <4C5F4314.7000107@cygwin.com> (raw)
In-Reply-To: <4C5DC614.7040105@tlinx.org>

On 8/7/2010 4:46 PM, Linda Walsh wrote:
> I'm willing to try again if anything has improved.  But there were also
> issues about me signing off contracts to Redhat or something -- not
> something normal to most open source projects...and that was a bit of a
> put off as well.  Has anything changed?

I believe you are confused.  There are no "contracts" involved to build
Cygwin.  You would be asked to fill out an assignment form if you're
contributing anything of significant amount back (with what constitutes
significant being defined by Red Hat).  I won't speculate about the
particular conversation you refer to and how this came up or to what it
was referring specifically.  But if you're just looking for instructions
on building Cygwin, they're in the FAQ:

<http://cygwin.com/faq/faq-nochunks.html#faq.programming.building-cygwin>

I'll let you be the judge of whether anything there has changed from the
last time you tried to build the DLL.  It is, however, worth noting that
building the DLL is *not* necessary to build mkpasswd.  Certainly it's
easiest if you just grab the source for everything from CVS but if you're
just looking to be able to debug your mkpasswd issue, I'd recommend foregoing
any efforts, at least at the moment, to build the Cygwin DLL.  You won't need
to do that to investigate the problem with which you started this thread.

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

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

      parent reply	other threads:[~2010-08-08 23:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-30 11:32 Linda Walsh
2010-07-30 16:15 ` Larry Hall (Cygwin)
2010-08-02 23:19   ` Linda Walsh
2010-08-02 23:44     ` Larry Hall (Cygwin)
2010-08-07 20:46       ` Linda Walsh
2010-08-07 22:52         ` Christopher Faylor
2010-08-08 23:51         ` Larry Hall (Cygwin) [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=4C5F4314.7000107@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).