Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <61f6f43905041107485bf456d7@mail.gmail.com> Date: Mon, 11 Apr 2005 10:48:30 -0400 From: Jim Drash Reply-To: Jim Drash To: Jan.Schormann@brainlab.com, cygwin@cygwin.com Subject: Re: FDA-conform validation - any hints? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: X-IsSubscribed: yes On Apr 11, 2005 9:48 AM, Jan Schormann wrote: > Hi all, > > my company develops medical devices, so we must fulfill > the FDA (U.S. Food & Drug Administration) regulations. > As we are using Cygwin in our software build chain > (especially for GNU make and bash), we need to explain > what makes us so confident. > > I've scanned the archives with no satisfying outcome, so ... > > Has anyone ever tried this before? > Do you have any hints? > FDA Validation in your case is about telling how you do your builds and showing that you follow what you say. I am not sure what you are looking for. -- 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/