On Tue, Dec 09, 2008 at 08:24:09AM +0100, Simon Josefsson wrote:
> Maybe you could disable C99 in the gnulib directory?
I remember doing so a while ago and getting detection errors. It's
commented out in my Makefile.am ;)
--
Sylvain
Sylvain Beucler <[EMAIL PROTECTED]> writes:
> On Sun, Dec 07, 2008 at 04:11:34PM -0800, Ben Pfaff wrote:
>> Brian Dessent <[EMAIL PROTECTED]> writes:
>>
>> > MinGW implements access to 'environ' as a macro in stdlib.h, one which
>> > gets the environment pointer through a function call. However,
On Sun, Dec 07, 2008 at 04:11:34PM -0800, Ben Pfaff wrote:
> Brian Dessent <[EMAIL PROTECTED]> writes:
>
> > MinGW implements access to 'environ' as a macro in stdlib.h, one which
> > gets the environment pointer through a function call. However, that
> > macro is not enabled if __STRICT_ANSI__ i
Brian Dessent <[EMAIL PROTECTED]> writes:
> MinGW implements access to 'environ' as a macro in stdlib.h, one which
> gets the environment pointer through a function call. However, that
> macro is not enabled if __STRICT_ANSI__ is set, and -std=c99 sets
> __STRICT_ANSI__. So one workaround would
Sylvain Beucler wrote:
> I imported module 'putenv'.
Did you also add the stdlib module?
> /usr/src/t/freedink-1.08.20081207/cross/gnulib/lib/../../../gnulib/lib/putenv.c:107:
> undefined reference to `_environ'
> /usr/src/t/freedink-1.08.20081207/cross/gnulib/lib/../../../gnulib/lib/putenv.c:1
Hello,
I imported module 'putenv'.
When cross-compiling through mingw32, I get the following errors at link time:
i586-mingw32msvc-gcc -g -O2 -Wall -std=c99
-I/usr/local/i586-mingw32msvc/include
-I/usr/local/i586-mingw32msvc/lib/libffi-3.0.7/include
-I/usr/local/i586-mingw32msvc/include/
