Re: XTerm always gives out an error message concerning a font

2017-07-12 Thread Thomas Dickey
- Original Message - | From: "Wouter van Doorn" | To: "Brian Inglis" , cygwin@cygwin.com | Sent: Thursday, July 6, 2017 5:31:42 PM | Subject: Re: XTerm always gives out an error message concerning a font | | No luck with either of the fixed-medium suggestions. The one you | mentioned as d

Re: Starting from a Windows Command Prompt

2017-07-12 Thread Brian Inglis
On 2017-07-12 14:15, Andrey Repin wrote: > Brian Inglis wrote: >> On 2017-07-12 00:16, Ugly Leper wrote: >>> Starting from a Windows Command Prompt, and using a syntax recommended >>> from years ago I still start a bash shell with >>> start /wait bin\bash (i.e. not just bin\bash) >>> and a mintty s

Re: Starting from a Windows Command Prompt

2017-07-12 Thread Andrey Repin
Greetings, Brian Inglis! > On 2017-07-12 00:16, Ugly Leper wrote: >> Starting from a Windows Command Prompt, and using a syntax recommended >> from years ago I still start a bash shell with >> start /wait bin\bash (i.e. not just bin\bash) >> and a mintty shell with >> start bin\mintty (i.e. not ju

Re: Starting from a Windows Command Prompt

2017-07-12 Thread Brian Inglis
On 2017-07-12 00:16, Ugly Leper wrote: > Starting from a Windows Command Prompt, and using a syntax recommended > from years ago I still start a bash shell with > start /wait bin\bash (i.e. not just bin\bash) > and a mintty shell with > start bin\mintty (i.e. not just bin\mintty) > and yet experime

Re: Pthreads: Prototypes missing if -std=c11

2017-07-12 Thread Yaakov Selkowitz
On 2017-07-12 11:15, bz0...@tirol.com wrote: > gcc does not recognize some functions from pthread.h if option -std=c11 is > used: Exactly, and the same happens with glibc. When you use -std=c*, that means you are declaring strict ISO C, and all extensions are disabled by default unless explicitl

Re: [cygwin] Re: Weird mintty behavior - windows 10

2017-07-12 Thread Thomas Wolff
Am 12.07.2017 um 04:30 schrieb Jason Pyeron: -Original Message- From: Thomas Wolff Sent: Tuesday, July 11, 2017 1:03 AM Am 11.07.2017 um 06:43 schrieb Jason Pyeron: When launching C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico - (from the start menu) And while in the terminal I hit C

Pthreads: Prototypes missing if -std=c11

2017-07-12 Thread bz0815
Hello, gcc does not recognize some functions from pthread.h if option -std=c11 is used: #include #define THREADS 5 int main (int argc, char *argv[]) { pthread_barrier_t barrier; pthread_barrier_init(&barrier, NULL, THREADS); } gcc -std=c11 -o test test.c test.c: In function ‘main’: test.c:

A success installing Dataplot using Cygwin, thanks to this list

2017-07-12 Thread Ian Lambert via cygwin
Question: Would this software be a candidate for a Cygwin package? Disclaimer: My testing has been minimal so far, but the X GUI and command line versions seem to work OK. "Dataplot® is a free, public-domain, multi-platform (Unix, Linux, Mac OS X, Windows XP/VISTA/7/8/10) software system for sc

Re: 64 bit g++ 5.4.0 bug

2017-07-12 Thread Takashi Yano
I have confirmed this problem disappears in Cygwin 2.8.2-1. Thanks. On Wed, 12 Jul 2017 22:12:12 +0900 Takashi Yano wrote: > Hello. > > I have encountered a weird behaviour of g++ compiler. > > If the following code is compiled with -ansi -O flags, > the resulting executable causes core dump.

64 bit g++ 5.4.0 bug

2017-07-12 Thread Takashi Yano
Hello. I have encountered a weird behaviour of g++ compiler. If the following code is compiled with -ansi -O flags, the resulting executable causes core dump. This is caused only in 64 bit environment. In 32 bit environment, it works as expected. $ cat str.cc #include int main() { std:

[ANNOUNCEMENT] Updated: Cygwin 2.8.2-1

2017-07-12 Thread Corinna Vinschen
Hi folks, I uploaded a new Cygwin release 2.8.2-1 This is mostely a bugfix release. === What's new: --- - New API: fls, flsl, flsll. Bug Fixes - - Fix scandirat Addresses: https://cygwin.com/ml/cygwin/201

Re: Starting from a Windows Command Prompt

2017-07-12 Thread Andrey Repin
Greetings, Ugly Leper! > Starting from a Windows Command Prompt, and using a syntax recommended > from years ago I still start a bash shell with > start /wait bin\bash (i.e. not just bin\bash) > and a mintty shell with mintty is not a shell, it's a terminal emulator. > start bin\mintty (i.e. not

Re: mkdir(2) prefers EACCES over EEXIST

2017-07-12 Thread Corinna Vinschen
On Jul 11 21:12, Christopher Wellons wrote: > This isn't _really_ a bug, more of an oddity. Calling mkdir(2) on an > existing directory will fail with EACCES instead of EEXIST if the directory > couldn't have been created in the first place. For example, this is the > typical situation for /cygdriv