Re: Recent change to terminal icon / mintty breaks taskbar pinning

[Adam Dinwoodie]

On Wed, Nov 11, 2015 at 09:53:29AM +0100, Corinna Vinschen wrote:
> On Nov 11 06:53, Andrey Repin wrote:
> > Greetings, Brian Mathis!
> > 
> > > I recently updated to the latest set of cygwin packages, and something
> > > has broken the terminal icon when pinned to the start menu.  When
> > > starting from the Start menu "Cygwin Terminal" icon, mintty comes up
> > > normally, loads my user profile, and the cwd is set to ~.
> > 
> > > However, if I right-click the icon on the taskbar and select "Pin to
> > > taskbar", close the existing terminal, then open by clicking on the
> > > pinned taskbar icon, the terminal starts but it does not load the
> > > profile, the cwd is /usr/bin, and no commands can be found (e.g. ls:
> > > command not found).  I have tracked this down to the pinned icon
> > > missing the arguments "-i /Cygwin-Terminal.ico -".
> > 
> > > I'm sure this worked prior to the update, so something seems to have
> > > changed.  I update fairly often, so this is something recent within
> > > the past month or so.  I'm on Windows 8.1 x64 using Cygwin 32bit.
> > 
> > I've experienced this same issue across a wide range of applications,
> > including AD management tools.
> > 
> > I have a feeling this is unrelated to Cygwin.
> 
> Yeah, pinning is only controlled by Windows itself (shell32
> functionality, probably).  It's not under the control of the
> application the shortcut points to.

Not so.  This is related to the recent MinTTY changes[0].  I get the
bugged behaviour on v2.2.1-0, but if I downgrade to v2.1.5-0, I get the
behaviour Brian is describing as correct, with the command line
arguments preserved when the program is pinned.

I'll guess this is, in particular, related to the "optional Windows
taskbar integration" listed in the changelog in the announcement email.

[0] https://cygwin.com/ml/cygwin-announce/2015-11/msg00020.html

--
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: Recent change to terminal icon / mintty breaks taskbar pinning

[Corinna Vinschen]

On Nov 11 06:53, Andrey Repin wrote:
> Greetings, Brian Mathis!
> 
> > I recently updated to the latest set of cygwin packages, and something
> > has broken the terminal icon when pinned to the start menu.  When
> > starting from the Start menu "Cygwin Terminal" icon, mintty comes up
> > normally, loads my user profile, and the cwd is set to ~.
> 
> > However, if I right-click the icon on the taskbar and select "Pin to
> > taskbar", close the existing terminal, then open by clicking on the
> > pinned taskbar icon, the terminal starts but it does not load the
> > profile, the cwd is /usr/bin, and no commands can be found (e.g. ls:
> > command not found).  I have tracked this down to the pinned icon
> > missing the arguments "-i /Cygwin-Terminal.ico -".
> 
> > I'm sure this worked prior to the update, so something seems to have
> > changed.  I update fairly often, so this is something recent within
> > the past month or so.  I'm on Windows 8.1 x64 using Cygwin 32bit.
> 
> I've experienced this same issue across a wide range of applications,
> including AD management tools.
> 
> I have a feeling this is unrelated to Cygwin.

Yeah, pinning is only controlled by Windows itself (shell32
functionality, probably).  It's not under the control of the
application the shortcut points to.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


pgpdR_9neVVmV.pgp
Description: PGP signature

Re: Octave audio issues reading wav files

[Marco Atzeri]

On 11/11/2015 08:37, Stan Moore wrote:

I have a 32 bit install with a possible audio issue in Octave 4.0.0-2.

My primary machine is unavailable right now but I think I can come up with a
STC from memory.

wavread("somefile.wav")

leads to a message about missing sndfile and that audioinfo can't work.

The issue seems to be octave was built on a machine without libsndfile so
config.h
sets HAS_SNDFILE to 0 which causes audioinfo to fail. A quick look at
audioinfo source
shows that most of the function is skipped unless HAS_SNDFILE is true.


Noted. I will look for next release.


I tried building local to check my theory out but ran into another possible
issue.
It seems libqrupdate 1.1.2-1 may have a problem.

/usr/lib/libqrupdate.la seems to (internally) include dependencies on files:
/usr/lib/liblapack.la and /usr/lib/libblas.la
which don't exist so local builds fail with something like:
/usr/bin/grep: /usr/lib/liblapack.la file does not exist



as workaround remove
/usr/lib/libqrupdate.la



If any of the above is wrong or confused I will be happy to back up and
provide cygcheck and generally better
information.

Stan


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



--
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: Recent change to terminal icon / mintty breaks taskbar pinning

[Corinna Vinschen]

On Nov 11 10:32, Adam Dinwoodie wrote:
> On Wed, Nov 11, 2015 at 09:53:29AM +0100, Corinna Vinschen wrote:
> > On Nov 11 06:53, Andrey Repin wrote:
> > > Greetings, Brian Mathis!
> > > 
> > > > I recently updated to the latest set of cygwin packages, and something
> > > > has broken the terminal icon when pinned to the start menu.  When
> > > > starting from the Start menu "Cygwin Terminal" icon, mintty comes up
> > > > normally, loads my user profile, and the cwd is set to ~.
> > > 
> > > > However, if I right-click the icon on the taskbar and select "Pin to
> > > > taskbar", close the existing terminal, then open by clicking on the
> > > > pinned taskbar icon, the terminal starts but it does not load the
> > > > profile, the cwd is /usr/bin, and no commands can be found (e.g. ls:
> > > > command not found).  I have tracked this down to the pinned icon
> > > > missing the arguments "-i /Cygwin-Terminal.ico -".
> > > 
> > > > I'm sure this worked prior to the update, so something seems to have
> > > > changed.  I update fairly often, so this is something recent within
> > > > the past month or so.  I'm on Windows 8.1 x64 using Cygwin 32bit.
> > > 
> > > I've experienced this same issue across a wide range of applications,
> > > including AD management tools.
> > > 
> > > I have a feeling this is unrelated to Cygwin.
> > 
> > Yeah, pinning is only controlled by Windows itself (shell32
> > functionality, probably).  It's not under the control of the
> > application the shortcut points to.
> 
> Not so.  This is related to the recent MinTTY changes[0].  I get the
> bugged behaviour on v2.2.1-0, but if I downgrade to v2.1.5-0, I get the
> behaviour Brian is describing as correct, with the command line
> arguments preserved when the program is pinned.
> 
> I'll guess this is, in particular, related to the "optional Windows
> taskbar integration" listed in the changelog in the announcement email.

Oh, ok, I didn't know that.  Thanks for clarifying.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


pgprvJTWCydpi.pgp
Description: PGP signature

Re: Documentation problem with the UG - POSIX devices?

[Corinna Vinschen]

On Nov 11 16:22, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-posixdevices
> 
> In the paragraph starting "Block devices are accessible ..."
> 
> "... or the first partition on the third harddisk is 
> \device\harddisk2\partition1."
> 
> Shouldn't partition1 be the second partition, not the first?

No.  partition0 is a symlink pointing to DR0, which in turn is the
entire physical disk.  As admin:

  $ ls -l /proc/sys/Device/Harddisk0 | grep DR0
  brwxrwx--x 1 Administrators SYSTEM 0, 250 Nov 11 17:32 DR0
  lr--r--r-- 1 Administrators SYSTEM  0 Nov 11 17:32 Partition0 -> 
/proc/sys/Device/Harddisk0/DR0
  $ ls -l /proc/sys/GLOBAL\?\? | grep DR0
  lr--r--r-- 1 Administrators SYSTEM0 Nov 11 17:32 
Disk{2b5b33fa-7185-944d-98ae-4ff14c0e5391} -> /proc/sys/Device/Harddisk0/DR0
  lr--r--r-- 1 Administrators SYSTEM0 Nov 11 17:32 PhysicalDrive0 -> 
/proc/sys/Device/Harddisk0/DR0

So the real partitioning starts with partition1, since partition0 is a
link to the physical disk as a whole.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


pgpE_6PPfV8ks.pgp
Description: PGP signature

Documentation problem with the UG - POSIX devices?

[Buchbinder, Barry (NIH/NIAID) [E]]

https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-posixdevices

In the paragraph starting "Block devices are accessible ..."

"... or the first partition on the third harddisk is 
\device\harddisk2\partition1."

Shouldn't partition1 be the second partition, not the first?

Best wishes,

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.


--
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: Octave audio issues reading wav files

[Stan Moore]

On 11/11/2015 Marco Atzeri wrote:
> On 11/11/2015 08:37, Stan Moore wrote:
> > I have a 32 bit install with a possible audio issue in Octave 4.0.0-2.
> >
> > My primary machine is unavailable right now but I think I can come up
> > with a STC from memory.
> >
> > wavread("somefile.wav")
> >
> > leads to a message about missing sndfile and that audioinfo can't work.
> >
> > The issue seems to be octave was built on a machine without libsndfile
> > so config.h sets HAS_SNDFILE to 0 which causes audioinfo to fail. A
> > quick look at audioinfo source shows that most of the function is
> > skipped unless HAS_SNDFILE is true.
> 
> Noted. I will look for next release.

Thanks, glad you could follow my "not very precise" ramblings.

> > I tried building local to check my theory out but ran into another
> > possible issue.
> > It seems libqrupdate 1.1.2-1 may have a problem.
> >
> > /usr/lib/libqrupdate.la seems to (internally) include dependencies on
files:
> > /usr/lib/liblapack.la and /usr/lib/libblas.la which don't exist so
> > local builds fail with something like:
> > /usr/bin/grep: /usr/lib/liblapack.la file does not exist
> 
> > as workaround remove
> /usr/lib/libqrupdate.la

I already did that and for the record the build completed.

Stan


--
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: Recent change to terminal icon / mintty breaks taskbar pinning

[cyg Simple]

On 11/11/2015 7:12 AM, Corinna Vinschen wrote:
> On Nov 11 10:32, Adam Dinwoodie wrote:
>> On Wed, Nov 11, 2015 at 09:53:29AM +0100, Corinna Vinschen wrote:
>>> On Nov 11 06:53, Andrey Repin wrote:
 Greetings, Brian Mathis!

> I recently updated to the latest set of cygwin packages, and something
> has broken the terminal icon when pinned to the start menu.  When
> starting from the Start menu "Cygwin Terminal" icon, mintty comes up
> normally, loads my user profile, and the cwd is set to ~.

> However, if I right-click the icon on the taskbar and select "Pin to
> taskbar", close the existing terminal, then open by clicking on the
> pinned taskbar icon, the terminal starts but it does not load the
> profile, the cwd is /usr/bin, and no commands can be found (e.g. ls:
> command not found).  I have tracked this down to the pinned icon
> missing the arguments "-i /Cygwin-Terminal.ico -".

> I'm sure this worked prior to the update, so something seems to have
> changed.  I update fairly often, so this is something recent within
> the past month or so.  I'm on Windows 8.1 x64 using Cygwin 32bit.

 I've experienced this same issue across a wide range of applications,
 including AD management tools.

 I have a feeling this is unrelated to Cygwin.
>>>
>>> Yeah, pinning is only controlled by Windows itself (shell32
>>> functionality, probably).  It's not under the control of the
>>> application the shortcut points to.
>>
>> Not so.  This is related to the recent MinTTY changes[0].  I get the
>> bugged behaviour on v2.2.1-0, but if I downgrade to v2.1.5-0, I get the
>> behaviour Brian is describing as correct, with the command line
>> arguments preserved when the program is pinned.
>>
>> I'll guess this is, in particular, related to the "optional Windows
>> taskbar integration" listed in the changelog in the announcement email.
> 
> Oh, ok, I didn't know that.  Thanks for clarifying.

Yes indeed thanks for clarifying.  The issue exists regardless of if you
pin the running task or you pin the Desktop icon.  Pinning the Desktop
icon will cause a new icon on the taskbar when MinTTY is executing.
Pinning the open task will cause subsequent task to bypass initial
startup and be sitting in /usr/bin instead of $HOME.

-- 
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: failure notice

[Mario Roy]

File locking is failing with Cygwin 2.4.0-0.2 as well. Thank you for
allowing the possibility of downgrading the Cygwin base package down
to 2.2.1-1 via setup.

Best regards,
Mario

--
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: Cygwin DLL V2.3.0 on XP 64-bit professional not working at all

[Georg Rehfeld]

-

Finally I restored the complete cygwin folder from a backup. Now Cygwin
works again as a charm. I conclude, that my system itself is OK and
something or the other might be broken in the current Cygwin version?


I once had this fork-error after a cygwin-update on windows 10. I
rebooted windows and all worked normal. Maybe that's what happened to
you also?


Thanks for the suggestion, but missing reboots are not the problem for
sure. As indicated I tried the base installs several times, always
alternating between 32bit and 64bit, always using a different mirror
and rebooted often (~10 times in the last day). Missing reboots also
should not cause the post install errors on the 32bit version IMHO.

Side note, if you wonder: XP 64 never got a service pack 3, only SP2.
And my system IS up to the last MS update.

Might be, I finally should update to W7 64, if XP 64 isn't supported
(any longer) by Cygwin.

Best regards, Georg
--
  ___   ___
 | + | |__Georg Rehfeld  Woltmanstr. 12 20097 Hamburg
 |_|_\ |___   rehf...@georg-rehfeld.de   +49 (40) 23 53 27 10

--
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: Cygwin DLL V2.3.0 on XP 64-bit professional not working at all

[Helmut Karlowski]

---
> Finally I restored the complete cygwin folder from a backup. Now Cygwin
> works again as a charm. I conclude, that my system itself is OK and
> something or the other might be broken in the current Cygwin version?

I once had this fork-error after a cygwin-update on windows 10. I 
rebooted windows and all worked normal. Maybe that's what happened to 
you also?

-Helmut


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

Cygwin DLL V2.3.0 on XP 64-bit professional not working at all

[Georg Rehfeld]

Dear all,

since yesterday I had a working Cygwin 32 running (since years) on my
XP 64 prof box. When I tried to update tonight I got errors in post
install (see below) and afterwards I could not start any cygwin
program, not even bash or grep (tried from a cmd prompt), without any
error message. After trying to reinstall from different mirrors,
rebooting several times I finally uninstalled cygwin completely as of
the FAQ (except for my cygwin/home/*) and installed a fresh base.
Without success.

*** 32bit, Setup version 2.873:

Postinstall script errors (same as with my previous update attempt:
-
Package: 0/Perpetual
0p_000_autorebase.dash exit code -1073741819
Package: _/base-cygwin
000-cygwin-post-install.sh exit code -1073741819
Package: _/_update-info-dir
update-info-dir.sh exit code -1073741819
Package: _/coreutils
coreutils.sh exit code -1073741819
Package: _/bash
bash.sh exit code -1073741819
Package: _/base-files
base-files-mketc.sh exit code -1073741819
base-files-profile.sh exit code -1073741819
Package: _/ca-certificates
ca-certificates.sh exit code -1073741819
Package: _/lynx
lynx.sh exit code -1073741819
Package: _/man-db
man-db.sh exit code -1073741819
Package: _/mintty
mintty.sh exit code -1073741819
-

When I try to start bash, the window opens and closes immediately. When
I open cmd.exe and try Cygwin commands e.g. 'bash' or 'grep ...' or
'man ...' there is no output at all; the command is found, but no
stdout or stderr or stackdump.

I'll attach the end of the setup.log.full.

cygcheck -s -v -r > cygcheck_32bit.out (run from cmd.exe) gave an error:
  garbled output from 'id' command - no uid= found
then hung with using 25% cpu (1 of my 4 cores), but still produced
output, which I attach.

I deleted the 32bit version as of FAQ and tried a base install of 64bit.

*** 64bit, Setup version 2.873:

The setup ran smooth, I can start bash. But e.g a 'ls' gives me errors
and a bash.exe.stackdump (attached). The errors are:
-
$ ls
  0 [main] bash 2356 F:\cygwin\bin\bash.exe: *** fatal error in 
forked process - fork: can't reserve memory for parent stack 0x14 - 
0x34, (child has 0x3 - 0x23), Win32 error 487
   2312 [main] bash 2356 cygwin_exception::open_stackdumpfile: Dumping 
stack trace to bash.exe.stackdump
  1 [main] bash 4356 fork: child -1 - forked process 2356 died 
unexpectedly, retry 0, exit code 0x100, errno 11

bash: fork: retry: No child processes
1006256 [main] bash 4872 F:\cygwin\bin\bash.exe: *** fatal error in 
forked process - fork: can't reserve memory for parent stack 0x14 - 
0x34, (child has 0x3 - 0x23), Win32 error 487
1006797 [main] bash 4872 cygwin_exception::open_stackdumpfile: Dumping 
stack trace to bash.exe.stackdump
2591368 [main] bash 4356 fork: child -1 - forked process 4872 died 
unexpectedly, retry 0, exit code 0x100, errno 11

bash: fork: retry: No child processes
4597941 [main] bash 1540 F:\cygwin\bin\bash.exe: *** fatal error in 
forked process - fork: can't reserve memory for parent stack 0x14 - 
0x34, (child has 0x3 - 0x23), Win32 error 487
4599025 [main] bash 1540 cygwin_exception::open_stackdumpfile: Dumping 
stack trace to bash.exe.stackdump
5849328 [main] bash 4356 fork: child -1 - forked process 1540 died 
unexpectedly, retry 0, exit code 0x100, errno 11

bash: fork: retry: No child processes
9855748 [main] bash 976 F:\cygwin\bin\bash.exe: *** fatal error in 
forked process - fork: can't reserve memory for parent stack 0x14 - 
0x34, (child has 0x3 - 0x23), Win32 error 487
9856620 [main] bash 976 cygwin_exception::open_stackdumpfile: Dumping 
stack trace to bash.exe.stackdump
11107304 [main] bash 4356 fork: child -1 - forked process 976 died 
unexpectedly, retry 0, exit code 0x100, errno 11

bash: fork: retry: No child processes
19114176 [main] bash 3372 F:\cygwin\bin\bash.exe: *** fatal error in 
forked process - fork: can't reserve memory for parent stack 0x14 - 
0x34, (child has 0x3 - 0x23), Win32 error 487
19114675 [main] bash 3372 cygwin_exception::open_stackdumpfile: Dumping 
stack trace to bash.exe.stackdump
20714816 [main] bash 4356 fork: child -1 - forked process 3372 died 
unexpectedly, retry 0, exit code 0x100, errno 11

bash: fork: Resource temporarily unavailable
-

When trying Cygwin commands from a cmd.exe prompt, commands seem to
work, e.g. a simple 'ls' or 'grep --help' or 'grep -i insert some.sql'
or 'vi some.sql'. But I did not test very much.

Output of cygcheck -s -v -r > cygcheck_64bit.out attached.

*** Restoring Cygwin from backup

Finally I restored the complete cygwin folder from a backup. Now Cygwin
works again as a charm. I conclude, that my system itself is OK and
something or the other might be broken in the current Cygwin version?

Any help is welcome, because I want to be able to update Cygwin in the
future. If I shall do some tests 

2.3.0: possible Cygwin flock bug (Windows 10 x86_64)

[Mario Roy]

Greetings,

During testing of the Perl MCE 1.608 module (uses flock), the examples
scripts hang. Downgrading the base Cygwin package from 2.3.0-1 to
2.2.1-1 resolves the issue.

Installation is not required if a Cygwin developer desires to test
file locking via the Perl MCE module.

https://cpan.metacpan.org/authors/id/M/MA/MARIOROY/MCE-1.608.tar.gz

1. extract tar file
2. cd MCE-1.608/examples
3. perl foreach.pl 10

Hangs with Cygwin 2.3.0-1
Successful with Cygwin 2.2.1-1

The upcoming Perl MCE 1.7 release does away with file locking and
works with 2.3.0-1. The next commit into GitHub (in a day or two) will
contain optimizations allowing Perl MCE on Windows and Cygwin to run
at full speed with lesser overhead.

Best regards,
Mario

p.s. Thank you for Cygwin

--
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: Updated: Cygwin 2.3.0-1

[Nem W Schlecht]

On Mon, Nov 9, 2015 at 4:51 AM, Corinna Vinschen
 wrote:
> Hi Cygwin friends and users,
>
> I released another version of Cygwin.  The version number is 2.3.0-1.
...
>
> - Fix EIO error accessing certain (OS X SMB?) drives
>   Addresses: https://cygwin.com/ml/cygwin/2015-09/msg00229.html
>

Just wanted to confirm - this fix worked perfectly for me.  I'm now
able to see my 3GB shared drive from from my Mac correctly in cygwin!

Thanks much!

-- 
Nem W Schlecht
 "Perl did the magic.  I just waved the wand."

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

gcc 4.9.2/4.9.3/5.2.0 segfault with aircrack-ng revision 2719

[tdotreppe]

After upgrading from 2.2.1 (IIRC) to 2.3.0 (32bit, on Windows 7 64 bit), 
Aircrack-ng makes gcc segfault. Every version available from the 
installer segfaults.


It is weird since I compiled it using gcc 5.2 on FreeBSD, gcc 4.9.2 on 
Debian 8 without any problem.


$ make
make -C src all
make[1]: Entering directory '/home/Thomas/aircrack-ng-trunk/src'
gcc -g -W -Wall -O3 -D_FILE_OFFSET_BITS=64 -D_REVISION=2719  -DCYGWIN 
-fstack-protector-strong -Wno-unused-but-set-variable -Wno-array-bounds 
-Iinclude   -c -o aircrack-ng.o aircrack-ng.c

gcc: internal compiler error: Segmentation fault (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
: recipe for target 'aircrack-ng.o' failed
make[1]: *** [aircrack-ng.o] Error 4
make[1]: Leaving directory '/home/Thomas/aircrack-ng-trunk/src'
Makefile:25: recipe for target 'all' failed
make: *** [all] Error 2

Here is gcc info (4.9.2-3):

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-cygwin/4.9.2/lto-wrapper.exe
Target: i686-pc-cygwin
Configured with: 
/cygdrive/i/szsz/tmpp/gcc/gcc-4.9.2-3.i686/src/gcc-4.9.2/configure 
--srcdir=/cygdrive/i/szsz/tmpp/gcc/gcc-4.9.2-3.i686/src/gcc-4.9.2 
--prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin 
--libexecdir=/usr/libexec --datadir=/usr/share --localstatedir=/var 
--sysconfdir=/etc --libdir=/usr/lib --datarootdir=/usr/share 
--docdir=/usr/share/doc/gcc --htmldir=/usr/share/doc/gcc/html -C 
--build=i686-pc-cygwin --host=i686-pc-cygwin --target=i686-pc-cygwin 
--without-libiconv-prefix --without-libintl-prefix --libexecdir=/usr/lib 
--enable-shared --enable-shared-libgcc --enable-static 
--enable-version-specific-runtime-libs --enable-bootstrap 
--enable-__cxa_atexit --with-dwarf2 --with-arch=i686 --with-tune=generic 
--disable-sjlj-exceptions 
--enable-languages=ada,c,c++,fortran,java,lto,objc,obj-c++ 
--enable-graphite --enable-threads=posix --enable-libatomic 
--enable-libgomp --disable-libitm --enable-libquadmath 
--enable-libquadmath-support --enable-libssp --enable-libada 
--enable-libjava --enable-libgcj-sublibs --disable-java-awt 
--disable-symvers --with-ecj-jar=/usr/share/java/ecj.jar --with-gnu-ld 
--with-gnu-as --with-cloog-include=/usr/include/cloog-isl 
--without-libiconv-prefix --without-libintl-prefix --with-system-zlib 
--enable-linker-build-id

Thread model: posix
gcc version 4.9.2 (GCC)

Also happens with gcc 5.2.0-1:

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-cygwin/5.2.0/lto-wrapper.exe
Target: i686-pc-cygwin
Configured with: 
/cygdrive/i/szsz/tmpp/gcc/gcc-5.2.0-1.i686/src/gcc-5.2.0/configure 
--srcdir=/cygdrive/i/szsz/tmpp/gcc/gcc-5.2.0-1.i686/src/gcc-5.2.0 
--prefix=/usr --exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc 
--docdir=/usr/share/doc/gcc --htmldir=/usr/share/doc/gcc/html -C 
--build=i686-pc-cygwin --host=i686-pc-cygwin --target=i686-pc-cygwin 
--without-libiconv-prefix --without-libintl-prefix --libexecdir=/usr/lib 
--enable-shared --enable-shared-libgcc --enable-static 
--enable-version-specific-runtime-libs --enable-bootstrap 
--enable-__cxa_atexit --with-dwarf2 --with-arch=i686 --with-tune=generic 
--disable-sjlj-exceptions 
--enable-languages=ada,c,c++,fortran,java,lto,objc,obj-c++ 
--enable-graphite --enable-threads=posix --enable-libatomic 
--enable-libgomp --disable-libitm --enable-libquadmath 
--enable-libquadmath-support --enable-libssp --enable-libada 
--enable-libjava --enable-libgcj-sublibs --disable-java-awt 
--disable-symvers --with-ecj-jar=/usr/share/java/ecj.jar --with-gnu-ld 
--with-gnu-as --with-cloog-include=/usr/include/cloog-isl 
--without-libiconv-prefix --without-libintl-prefix --with-system-zlib 
--enable-linker-build-id

Thread model: posix
gcc version 5.2.0 (GCC)

And gcc 4.9.3-1:

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-cygwin/4.9.3/lto-wrapper.exe
Target: i686-pc-cygwin
Configured with: 
/cygdrive/i/szsz/tmpp/gcc/gcc-4.9.3-1.i686/src/gcc-4.9.3/configure 
--srcdir=/cygdrive/i/szsz/tmpp/gcc/gcc-4.9.3-1.i686/src/gcc-4.9.3 
--prefix=/usr --exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc 
--docdir=/usr/share/doc/gcc --htmldir=/usr/share/doc/gcc/html -C 
--build=i686-pc-cygwin --host=i686-pc-cygwin --target=i686-pc-cygwin 
--without-libiconv-prefix --without-libintl-prefix --libexecdir=/usr/lib 
--enable-shared --enable-shared-libgcc --enable-static 
--enable-version-specific-runtime-libs --enable-bootstrap 
--enable-__cxa_atexit --with-dwarf2 --with-arch=i686 --with-tune=generic 
--disable-sjlj-exceptions 
--enable-languages=ada,c,c++,fortran,java,lto,objc,obj-c++ 
--enable-graphite --enable-threads=posix --enable-libatomic 
--enable-libgomp --disable-libitm --enable-libquadmath 
--enable-libquadmath-support --enable-libssp --enable-libada 
--enable-libjava --enable-libgcj-sublibs --disable-java-awt 
--disable-symvers