Re: Symbol visibility problems with -std=

2020-05-13 Thread Yaakov Selkowitz
On Wed, 2020-05-13 at 13:21 +0300, Pavel Fedin via Cygwin wrote: > While compiling various software packages for Cygwin i notice that very > often i have to add something like #define _GNU_SOURCE to > them in order to compile correctly. Meanwhile on Linux they compile with no > problems at all.

Re: Symbol visibility problems with -std=

2020-05-13 Thread Csaba Ráduly via Cygwin
On 13/05/2020 14:12, Marco Atzeri via Cygwin wrote: Am 13.05.2020 um 12:21 schrieb Pavel Fedin via Cygwin: (snip code using strdup) $ g++ test.cpp -o test - compiles OK $ g++ test.cpp -o test -std=c++14 - error: 'strdup' was not declared in this scope; did you mean 'strcmp'? strdup is an

Re: Symbol visibility problems with -std=

2020-05-13 Thread Marco Atzeri via Cygwin
Am 13.05.2020 um 12:21 schrieb Pavel Fedin via Cygwin: Hello everyone! While compiling various software packages for Cygwin i notice that very often i have to add something like #define _GNU_SOURCE to them in order to compile correctly. Meanwhile on Linux they compile with no problems at a

Symbol visibility problems with -std=

2020-05-13 Thread Pavel Fedin via Cygwin
Hello everyone! While compiling various software packages for Cygwin i notice that very often i have to add something like #define _GNU_SOURCE to them in order to compile correctly. Meanwhile on Linux they compile with no problems at all. I've narrowed it down to -std=??? option using a simple