From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: cygwin@cygwin.com
Subject: Re: Problem during C source code compilation
Date: Thu, 06 Sep 2012 13:56:00 -0000 [thread overview]
Message-ID: <50489E19.5010208@cs.utoronto.ca> (raw)
In-Reply-To: <50489C52.3030608@hones.org.uk>
On 06/09/2012 8:51 AM, Cliff Hones wrote:
> 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.
While you're at it, look for the parts of the FAQ that talk about BLODA
and -- to a lesser degree -- fork failures.
Ryan
--
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
next prev parent reply other threads:[~2012-09-06 12:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 20:27 Fausto Arinos Barbuto
2012-09-05 20:47 ` Christopher Faylor
2012-09-06 12:51 ` Fausto Arinos Barbuto
2012-09-06 12:59 ` Cliff Hones
2012-09-06 13:56 ` Ryan Johnson [this message]
2012-09-06 21:45 ` Fausto Arinos Barbuto
2012-09-07 2:38 ` Yaakov (Cygwin/X)
2012-09-08 1:30 ` Fausto Arinos Barbuto
2012-09-09 12:45 ` Daniel Colascione
2012-09-09 17:30 ` Earnie Boyd
2012-09-10 2:38 ` JonY
2012-09-10 13:25 ` Earnie Boyd
2012-09-10 13:36 ` Sean Murphy
2012-09-06 14:58 ` Fausto Arinos Barbuto
2012-09-06 15:09 ` Ryan Johnson
2012-09-06 21:38 ` Fausto Arinos Barbuto
2012-09-06 20:34 ` Christopher Faylor
2012-09-10 12:55 ` SOLVED: " Fausto
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=50489E19.5010208@cs.utoronto.ca \
--to=ryan.johnson@cs.utoronto.ca \
--cc=cygwin@cygwin.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).