public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Problems with "Hello, World!"
Date: Sat, 23 Mar 2019 08:17:00 -0000	[thread overview]
Message-ID: <534338decdf116e0ba1aa68fc43de163@smtp-cloud8.xs4all.net> (raw)
In-Reply-To: <CAF0NPdiG0hTHs=+CF+RjEts+zom33yQf5iT59THCgSeGjpC_dg@mail.gmail.com>

On Fri, 22 Mar 2019 16:25:08, Vesa P dot "  wrote:

> > Rather than describing what you did, copy and paste a shell transcript showing
> > the commands and output from you listing the source code, compiling and running
> > it, a long listing of the directory contents, then run
> >
> >         "cygcheck -hrsv > cygcheck.out"
> >
> > and attach the output as a text file to a post to this list, as explained below
> > under Problem reports: http://cygwin.com/problems.html.
> 
> I included a modified version of cygcheck.out. Mostly sensitive letter
> sequences have been
> replaced by 6 X's: "XXXXXX".  And user groups in was all replaced by
> "/// User group names and numbers omitted ///"

Vesa,

From your previous post it was clear that your program did not execute. You
compiled your "hello.c" as follows:

    gcc -Wextra -Wall -o hello hello.c

You are using the 64-bits setup of Cygwin. Me too (although I have W7).

64-@@ uname -a
CYGWIN_NT-6.1 Seven 3.0.4(0.338/5/3) 2019-03-16 09:50 x86_64 Cygwin

 ** Me **
64-@@ grep gcc cygcheck-20190323.out
Found: E:\Cygwin64\bin\gcc.exe
   70k 2018/12/09 E:\Cygwin64\bin\cyggcc_s-seh-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggcc_s-seh-1.dll" v0.0 ts=2018-12-08 19:56
gcc-core                                7.4.0-1               OK
libgcc1                                 7.4.0-1               OK
(I deleted non-relevant output)

 ** Vesa **
64-@@ grep gcc cygcheck-vesa.out
Found: C:\Users\XXXXXX\cygwin64\bin\gcc.exe <==== What is this? (is this
  the compiler for the 32-bits setup of Cygwin?)
   70k 2018/06/26 C:\Users\XXXXXX\cygwin64\bin\cyggcc_s-seh-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggcc_s-seh-1.dll" v0.0 ts=2018-06-26 17:17
cygwin32-gcc-core         6.4.0-1             OK <==== generating code for
  the 32-bits setup of Cygwin ????? (I have forgotten)
cygwin32-gcc-g++          6.4.0-1             OK
libgcc1                   7.3.0-3             OK
-----

Q: where is your compiler (gcc)? Evidently you are not using the compiler
from the 64-bits setup ...

Btw, you are using an old version of Cygwin (cygwin1.dll) ... Why do you
not update (while also installing the 64-bits version of the compiler).

I may be wrong though (as I only skimmed your posts and the cygcheck.out
file).

Henri


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

  parent reply	other threads:[~2019-03-23  8:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 21:31 Vesa P.
2019-03-19 22:14 ` Thomas Wolff
2019-03-20  3:15 ` L A Walsh
2019-03-20  3:33 ` Brian Inglis
2019-03-22 14:25   ` Vesa P.
2019-03-22 18:58     ` Achim Gratz
2019-03-23  8:17     ` Houder [this message]
2019-03-23  8:33       ` Houder
2019-03-23  8:52         ` Houder
2019-03-25 13:35         ` Vesa P.

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=534338decdf116e0ba1aa68fc43de163@smtp-cloud8.xs4all.net \
    --to=houder@xs4all.nl \
    --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).