FW: gecko Segmentation fault when compiling

[Andrey Repin]

Greetings, tlake@twcny.rr.com!

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

From the very first page of http://cygwin.com/ :

What...
...is it?

Cygwin is:
 - a large collection of GNU and Open Source tools which provide functionality similar to a Linux distribution on Windows.
 - a DLL (cygwin1.dll) which provides substantial POSIX API functionality.

Ability to compile programs is almost a byproduct of ability to compile itself.

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

If you want to compile native Windows programs, Cygwin is likely not the
tool you need.


-- 
With best regards,
Andrey Repin
Wednesday, August 29, 2018 17:57:40

Sorry for my terrible english...B‹KCB”›Ø›[H™\ܝΈ‹ËØÞYÝÚ[‹˜ÛÛKܛ؛[\Ëš[B‘TNˆ‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘ØÝ[Y[][ÛŽˆ‹ËØÞYÝÚ[‹˜ÛÛKÙØÜËš[B•[œÝXœØÜšX™H[™›Îˆ‹ËØÞYÝÚ[‹˜ÛÛKÛ[ÈÝ[œÝXœØÜšX™K\Ú[\CBƒB