Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 27 Jun 2001 20:40:58 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: "shouted down", "shot down", apologies Message-ID: <20010627204058.B26445@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <03F4742D8225D21191EF00805FE62B9908E23EDC AT aa-msg-01 DOT medstat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from bkeener@thesoftwaresource.com on Wed, Jun 27, 2001 at 08:32:52PM -0400 On Wed, Jun 27, 2001 at 08:32:52PM -0400, Brian Keener wrote: >John Wiersba wrote: >>As Brian Keener implied in his email, I don't really want to spend a >>huge amount of time just getting setup to successfully build the >>source, before I can even start to contribute. I routinely build perl >>and quite a few GNU packages on AIX, SunOS, HP/UX and linux, but all of >>them build relatively cleanly out-of-the-box with only minor tweaking. > >I think part of this is as Chris stated - maybe I over mystified some >of the problems I had/have and the step involved in being a contributor >or maybe it was/is my total lack of C++ programming on any platform and >cygwin knowledge before getting started. As a total newcomer to C++ >that found Cygwin very appealing and not having worked with anything >using a make or a makefile since a little bit of C work - getting >started on Cygwin was a challenge. I guess I just bit off too much to >start with Well, as a total newcomer, you made some amazing contributions to setup.exe so I'm very happy that you signed on. cgf -- 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/