Vadim Zeitlin vz-libtool at zeitlins.org writes:
And as this project build options also include -std=c++0x,
__STRICT_ANSI__ is defined. For the compiler I use it would be enough to
add _CRTIMP in front of the declaration as this is how _putenv() is really
declared in
On Thu, 23 Jun 2011 09:24:35 -0500 (CDT) Bob Friesenhahn
bfrie...@simple.dallas.tx.us wrote:
BF On Thu, 23 Jun 2011, Vadim Zeitlin wrote:
BF
BF I.e. it created a shared library with undefined symbols without any
BF problems because it never actually passed -no-undefined to g++/ld.
BF
BF In
On Thu, 23 Jun 2011, Vadim Zeitlin wrote:
I.e. it created a shared library with undefined symbols without any
problems because it never actually passed -no-undefined to g++/ld.
In actual practice, it seems difficult or impossible to build programs
under systems like Linux with -no-undefined.
Den 2011-06-23 14:25 skrev Vadim Zeitlin:
On Thu, 23 Jun 2011 13:12:42 +0200 Peter Rosin p...@lysator.liu.se wrote:
PR Den 2011-06-23 11:22 skrev Vadim Zeitlin:
PR I have no idea whether -no-undefined is supposed to work like this but
in
PR any case it seems to me that it's perfectly
On 6/23/2011 11:03 AM, Vadim Zeitlin wrote:
On Thu, 23 Jun 2011 09:24:35 -0500 (CDT) Bob Friesenhahn
bfrie...@simple.dallas.tx.us wrote:
BF On Thu, 23 Jun 2011, Vadim Zeitlin wrote:
BF
BF I.e. it created a shared library with undefined symbols without any
BF problems because it never
On 6/23/2011 5:34 AM, Vadim Zeitlin wrote:
Re-declaring _putenv() without _CRTIMP in strict ANSI mode when using MinGW
resulted in a warning because of a conflict with the previous declaration that
did use _CRTIMP.
Simply add _CRTIMP to our declaration to avoid it.
-int _putenv (const char
