public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: <tlake@twcny.rr.com>
To: <cygwin@cygwin.com>
Subject: RE: FW: gecko Segmentation fault when compiling
Date: Wed, 29 Aug 2018 13:05:00 -0000	[thread overview]
Message-ID: <!&!AAAAAAAAAAAuAAAAAAAAAOY+MTsETahCgLYsSiyFXC4BAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAADTTuYSOw5jSbvLEeBXqBMRAQAAAAA=@twcny.rr.com> (raw)
In-Reply-To: <774189134.20180829130119@yandex.ru>

> I uninstalled and deleted the entire cygwin64 directory and 
> reinstalled using the defaults. The download time was much shorter but 
> I still can't compile anything with the C compiler even with no anti-virus
running.

Base cygwin installation is a POSIX userspace and essential Cygwin tools, it
does not include any compilers at all, quite predictable.

> I'm surprised the default installation doesn't include make or dir.h.

Why it should?

Why? Because from a Windows perspective it seems like the whole purpose of
Cygwin is to be able to 
compile source code to run under Windows. It should include the tools to do
that in the default setup.

> Adding make was no problem but it took me a while to find a package 
> that contains dir.h.

I think we need a "build-essential" metapackage.

Exactly! I'm primarily a Windows programmer. I only compile Linux and Unix
programs when I have no other choice
and I certainly don't know all the ins and outs of those OSes. Anything that
makes Cygwin easier for Windows programmers is welcome!

Tom L



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

  reply	other threads:[~2018-08-29 11:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-25 12:44 tlake
2018-08-26 13:56 ` Marco Atzeri
     [not found]   ` <!&!AAAAAAAAAAAuAAAAAAAAAOY+MTsETahCgLYsSiyFXC4BAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAADPibjNochZQoAsZaGDyawCAQAAAAA=@twcny.rr.com>
2018-08-27  9:09     ` Marco Atzeri
2018-08-27 19:20       ` cyg Simple
2018-08-29 10:05         ` tlake
2018-08-29 11:16           ` Andrey Repin
2018-08-29 13:05             ` tlake [this message]
2018-08-30  6:40               ` Andrey Repin
2018-08-30  7:13                 ` tlake
2018-08-30  8:50             ` "build-essential" metapackage [WAS: FW: gecko Segmentation fault when compiling] cyg Simple
2018-08-30  9:30               ` Andrey Repin
2018-08-30  0:35           ` FW: gecko Segmentation fault when compiling Marco Atzeri

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=''\!'&'\!'AAAAAAAAAAAuAAAAAAAAAOY+MTsETahCgLYsSiyFXC4BAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAADTTuYSOw5jSbvLEeBXqBMRAQAAAAA=@twcny.rr.com' \
    --to=tlake@twcny.rr.com \
    --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).