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: Sun, 26 Aug 2018 13:56:00 -0000	[thread overview]
Message-ID: <40b87831-a714-80b9-a833-f9092a6e93e6@gmail.com> (raw)
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAOY+MTsETahCgLYsSiyFXC4BAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAADM9dbw/BZ6R4Fg0PvJbCjKAQAAAAA=@twcny.rr.com>

Am 25.08.2018 um 04:32 schrieb tlake@twcny.rr.com:
> can you upload somewhere ?
>
> Any Antivirus around ?
>
> Here's a link to my cygcheck.out file.
>
> I'm running Microsoft's anti-virus for Win 10 and Malwarebytes Premium.

can you test with these two disabled ?
Windows defender is known to interfere.

https://cygwin.com/faq/faq.html#faq.using.bloda

>
> https://www.dropbox.com/s/ta5v8ws04h5aggx/cygcheck.out?raw=1
>

 From what I see:

#1 you have 2 extra directories with possible colliding binary in front
of the cygwin one.

Path:   D:\cygwin64\mingw64\bin
         D:\cygwin64\d\LANGS\arm\bin
         D:\cygwin64\usr\local\bin
         D:\cygwin64\bin
...

  If you are mixing binaries between compilers and linkers a crash is
likely.

Can you test with just
PATH="/usr/local/bin:/usr/bin/:/usr/lib/lapack"

to exclude other programs ?

#2 you have installed every cygwin package including all
   debuginfo packages. Why ?
see https://cygwin.com/faq.html#faq.setup.everything

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

  reply	other threads:[~2018-08-25 20:13 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 [this message]
     [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           ` 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=40b87831-a714-80b9-a833-f9092a6e93e6@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).