public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Charles Wilson" <cwilson@ece.gatech.edu>, <jm.poure@freesurf.fr>
Cc: <cygwin@cygwin.com>
Subject: Re: RPM 4 under cygwin
Date: Thu, 20 Dec 2001 01:44:00 -0000	[thread overview]
Message-ID: <012401c1893a$a6dd6440$0200a8c0@lifelesswks> (raw)
In-Reply-To: <3C21A9B6.30702@ece.gatech.edu>

----- Original Message -----
From: "Charles Wilson" <cwilson@ece.gatech.edu>
> No, actually you are wrong -- this is not a demonstration of anything
of
> the sort.  Let us suppose that you COULD link cygwin1.dll statically
> (into rpm.exe?).  What mount table would be available for that
> cygwin-inside-rpm.exe to use?

As long as no absolute, non /cygdrive/ path access occurs, a static
linked cygwin1.dll would be sufficient for setup.exe. However other
issues still exist and I share your distate of the arrogant manner in
which the question?/statement?/whatever it was was communicated to us.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2001-12-20  9:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19  6:20 Jean-Michel POURE
2001-12-19  7:44 ` Larry Hall (RFK Partners, Inc)
2001-12-19  7:54   ` Prentis Brooks
2001-12-19  8:10   ` Jean-Michel POURE
2001-12-19  8:28     ` Larry Hall (RFK Partners, Inc)
2001-12-19  8:11   ` Charles Wilson
2001-12-19 13:47     ` Robert Collins
2001-12-20  0:47     ` Jean-Michel POURE
2001-12-20  0:47       ` Robert Collins
2001-12-20  1:10       ` Charles Wilson
2001-12-20  1:44         ` Robert Collins [this message]
2001-12-20  1:45           ` Robert Collins
2001-12-20  3:02         ` Jean-Michel POURE

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='012401c1893a$a6dd6440$0200a8c0@lifelesswks' \
    --to=robert.collins@itdomain.com.au \
    --cc=cwilson@ece.gatech.edu \
    --cc=cygwin@cygwin.com \
    --cc=jm.poure@freesurf.fr \
    /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).