public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: FW: gecko Segmentation fault when compiling
Date: Thu, 30 Aug 2018 00:35:00 -0000	[thread overview]
Message-ID: <6f0a5876-efd2-58df-55fd-4f4263a63571@gmail.com> (raw)
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAOY+MTsETahCgLYsSiyFXC4BAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAAA/cAkfad6fTJrryHc+HQGcAQAAAAA=@twcny.rr.com>

Am 29.08.2018 um 02:16 schrieb 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.
> I'm surprised the default installation doesn't include make or dir.h.
> Adding make was no problem but it took me a while to find a package that contains dir.h.
>
> Tom L
>

dir.h is surely not a standard header for building a cygwin program.
It is clearly only for cross compiling for Windows

$ cygcheck -p include/dir.h
Found 7 matches for include/dir.h
djgpp-runtime-2.05-1 - djgpp-runtime: DJGPP toolchain C runtime
(installed binaries and support files)
mingw64-i686-headers-5.0.2-1 - mingw64-i686-headers: MinGW-w64 runtime
headers and libraries
mingw64-i686-headers-5.0.3-1 - mingw64-i686-headers: MinGW-w64 runtime
headers and libraries
mingw64-i686-headers-5.0.4-1 - mingw64-i686-headers: MinGW-w64 runtime
headers and libraries
mingw64-x86_64-headers-5.0.2-1 - mingw64-x86_64-headers: MinGW-w64
runtime headers and libraries
mingw64-x86_64-headers-5.0.3-1 - mingw64-x86_64-headers: MinGW-w64
runtime headers and libraries
mingw64-x86_64-headers-5.0.4-1 - mingw64-x86_64-headers: MinGW-w64
runtime headers and libraries

sys/dir.h is another matter

$ cygcheck -p include/sys/dir.h
Found 7 matches for include/sys/dir.h
cygwin-devel-2.10.0-1 - cygwin-devel: Core development files
cygwin-devel-2.11.0-0.4 - cygwin-devel: Core development files
cygwin-devel-2.9.0-3 - cygwin-devel: Core development files
...

"cygcheck -p" and https://cygwin.com/packages/
are the basic tool to find any package component.

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
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:[~2018-08-29 13:20 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
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           ` Marco Atzeri [this message]

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=6f0a5876-efd2-58df-55fd-4f4263a63571@gmail.com \
    --to=marco.atzeri@gmail.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).