X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,TW_YG
X-Spam-Check-By:	sourceware.org
Message-ID:	<50489C52.3030608@hones.org.uk>
Date:	Thu, 06 Sep 2012 13:51:30 +0100
From:	Cliff Hones <cliff AT hones DOT org DOT uk>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Problem during C source code compilation
References:	<loom DOT 20120905T214546-374 AT post DOT gmane DOT org> <20120905202710 DOT GA10452 AT ednor DOT casa DOT cgf DOT cx> <loom DOT 20120906T142059-777 AT post DOT gmane DOT org>
In-Reply-To:	<loom.20120906T142059-777@post.gmane.org>
X-Spam-Score:	-0.0 (/) (knockando.watchfront.net.uk)
X-Spam-Report:	knockando.watchfront.net.uk has scanned this email for spam. Results:- T_RP_MATCHES_RCVD=-0.01 (total -0.0, current threshold 5.0)
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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 06/09/2012 13:40, Fausto Arinos Barbuto wrote:
> Christopher Faylor writes:
> 
>>
>> On Wed, Sep 05, 2012 at 07:49:57PM +0000, Fausto Arinos Barbuto wrote:
>>> Hello,
>>>
>>> I'm trying to compile a simple C source code but I'm getting the
>>> following error(s):
>>>
>>> $ gcc -o struct struct.c
>>
>> Start here: http://cygwin.com/problems.html
>>
> 
> Didn't help a whole lot, but thanks anyway.
> 
> Peering into the mailing list I found out that someone had had a
> barely similar problem and was suggested to reinstall binutils.
> I did that and it didn't work.  I also tried the FAQ -- to no
> avail.
> 
> Still have the problem.

But you didn't follow the advice in that link.  You said you were going
to warmly appreciate any advice - not ignore it!

One of the key parts, (and it is in bold) is:
   Run cygcheck -s -v -r > cygcheck.out and include that file as an attachment
   in your report. Please do not compress or otherwise encode the output. Just
   attach it as a straight text file so that it can be easily viewed.

-- Cliff


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -