X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 16 May 2008 17:13:31 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: compile problems on cygwin
Message-ID: <20080516211331.GB4611@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <714919 DOT 88697 DOT qm AT web55113 DOT mail DOT re4 DOT yahoo DOT com> <200805161735 DOT m4GHZSHi005168 AT pippin DOT first DOT lan> <alpine DOT LRH DOT 1 DOT 10 DOT 0805161530120 DOT 23139 AT arj DOT bjyevire DOT pbz> <alpine DOT LRH DOT 1 DOT 10 DOT 0805161628250 DOT 23139 AT arj DOT bjyevire DOT pbz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LRH.1.10.0805161628250.23139@arj.bjyevire.pbz>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Fri, May 16, 2008 at 04:31:59PM -0400, R P Herrold wrote:
>
> per (and uncharacteristically responding to myself):
>     http://cygwin.com/problems.html

That link also suggests against using the generic "I have a problem"
type of Subject and asks for some details.

> I attach the environment inventory, on the seeming missing #undef exposed 
> by the trading shim tarball at:
>     ftp://ftp.trading-shim.org/pub/local/trading-shim/attic/shim-080411.tgz
> which I reported here a few minutes ago.

Actually you alluded to a problem rather than actually reporting it.  There
were almost no details in your first email.

If it is something as simple as cygwin's gcc not honoring #undef then it
seems like a simple test case could demonstrate the problem.  Your
5,880,888 byte tar file doesn't really qualify.

Do you have a succint problem description and a simple test case which
describes it?

cgf

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