Re: FW: gecko Segmentation fault when compiling

Re: FW: gecko Segmentation fault when compiling

[tlake]

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.

 

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


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

Re: FW: gecko Segmentation fault when compiling

[Marco Atzeri]

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

Re: FW: gecko Segmentation fault when compiling

[Marco Atzeri]

reply on the mailing list please.

Am 26.08.2018 um 16:54 schrieb tlake@twcny.rr.com:
> can you test with these two disabled ?
> Windows defender is known to interfere.
>
> I'll try it but it was working fine before the last three builds of Windows. Nothing else has changed.

except may be they have changed something.

>
> Can you test with just
> PATH="/usr/local/bin:/usr/bin/:/usr/lib/lapack"
> to exclude other programs ?
>
> I just tried that. Same problem.
>
> #2 you have installed every cygwin package including all
>     debuginfo packages. Why ?
>
> I'd rather have it and not need it than need it and not have it.

a bit extreme as solution. you are just making everything slower
and heavier then needed.

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

Re: FW: gecko Segmentation fault when compiling

[cyg Simple]

On 8/26/2018 11:28 AM, Marco Atzeri wrote:
> Am 26.08.2018 um 16:54 schrieb tlake@twcny.rr.com:

>>
>> Can you test with just
>> PATH="/usr/local/bin:/usr/bin/:/usr/lib/lapack"
>> to exclude other programs ?
>>
>> I just tried that. Same problem.
>>
>> #2 you have installed every cygwin package including all
>>     debuginfo packages. Why ?
>>
>> I'd rather have it and not need it than need it and not have it.
> 
> a bit extreme as solution. you are just making everything slower
> and heavier then needed.
> 

Especially when you can add it if you need it.  Every path in the list
is searched at times so you're slowing down the responses when the PATH
is extreme.

-- 
cyg Simple

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

RE: FW: gecko Segmentation fault when compiling

[tlake]

>> Can you test with just
>> PATH="/usr/local/bin:/usr/bin/:/usr/lib/lapack"
>> to exclude other programs ?
>>
>> I just tried that. Same problem.
>>
>> #2 you have installed every cygwin package including all
>>     debuginfo packages. Why ?
>>
>> I'd rather have it and not need it than need it and not have it.
> 
> a bit extreme as solution. you are just making everything slower and 
> heavier then needed.
> 

Especially when you can add it if you need it.  Every path in the list is searched at times so you're slowing down the responses when the PATH is extreme.

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


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

Re: 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?

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


-- 
With best regards,
Andrey Repin
Wednesday, August 29, 2018 12:56:17

Sorry for my terrible english...


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

RE: FW: gecko Segmentation fault when compiling

[tlake]

> 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

Re: FW: gecko Segmentation fault when compiling

[Andrey Repin]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1949 bytes --]

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...\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

RE: FW: gecko Segmentation fault when compiling

[tlake]

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

If you can tell me another way to compile C source code that was written to
run under Linux
to run them on Windows without having to change them, I'm all ears! 

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

Re: "build-essential" metapackage [WAS: FW: gecko Segmentation fault when compiling]

[cyg Simple]

On 8/29/2018 6:01 AM, Andrey Repin wrote:
> 
> I think we need a "build-essential" metapackage.
> 

I would suggest base-devel as the name of the metapackage.  But what
exactly should that include?  Should there be more than one metapackage
that adds more complex tools?

-- 
cyg Simple

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

Re: "build-essential" metapackage [WAS: FW: gecko Segmentation fault when compiling]

[Andrey Repin]

Greetings, cyg Simple!

> On 8/29/2018 6:01 AM, Andrey Repin wrote:
>> 
>> I think we need a "build-essential" metapackage.
>> 

> I would suggest base-devel as the name of the metapackage.

build-essential is a name of a well-known Debian metapackage.

> But what exactly should that include?

Package: build-essential
State: not installed
Version: 12.1ubuntu2
Priority: optional
Section: devel
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: amd64
Uncompressed Size: 20,5 k
Depends: libc6-dev | libc-dev, gcc (>= 4:5.2), g++ (>= 4:5.2), make, dpkg-dev (>= 1.17.11)

In case of Cygwin, it should probably include autotools and cygport.

> Should there be more than one metapackage that adds more complex tools?

IDK, I'm not a developer myself.


-- 
With best regards,
Andrey Repin
Thursday, August 30, 2018 3:23:38

Sorry for my terrible english...


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

Re: FW: gecko Segmentation fault when compiling

[Marco Atzeri]

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