public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Shankar Unni" <shankar@cotagesoft.com>
To: <lhall@rfk.com>
Cc: <cygwin@cygwin.com>
Subject: RE: Distribute gcc minus gcj? (was Re: Questions about Cygwin's "jar" command)
Date: Mon, 23 Jun 2003 21:40:00 -0000	[thread overview]
Message-ID: <026f01c339b9$769a69f0$7e0aa8c0@HQSHANKAR> (raw)
In-Reply-To: <3EF749AF.1010303@rfk.com>

Larry Hall wrote:

> I know I shouldn't answer a question with a question but you 
> intend this to be rhetorical, right?
> 
> Never mind.  I'll bite.  If you or someone else is interested 
> in providing a gcj package, I expect Chris would work with that 
> person to avoid any package clash.

No, that wasn't what I meant. I was simply asking if it was possible for
(and acceptable to) cgf to drop "gcj" from the gcc package. (I.e. not
provide it at all).

What I said was that *if* there was some cygwin user who actually was going
to use gcj for something "real"(TM), they would also be able to build it for
themselves. (I.e. I'm asserting that dropping gcj is not going to cause
anyone any major heartburn).
--
Shankar.



--
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:[~2003-06-23 18:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 18:02 Questions about Cygwin's "jar" command David M. Karr
2003-06-22 19:43 ` Larry Hall
2003-06-23 18:59   ` Distribute gcc minus gcj? (was Re: Questions about Cygwin's "jar" command) Shankar Unni
2003-06-23 20:36     ` Larry Hall (RFK Partners, Inc.)
2003-06-23 21:40       ` Shankar Unni [this message]
2003-06-23 22:16         ` Larry Hall
2003-06-24  0:10         ` Markus Schönhaber

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='026f01c339b9$769a69f0$7e0aa8c0@HQSHANKAR' \
    --to=shankar@cotagesoft.com \
    --cc=cygwin@cygwin.com \
    --cc=lhall@rfk.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).