[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21446: Conflicting definitions in cwrapperexe
From: |
Peter Rosin |
Subject: |
bug#21446: Conflicting definitions in cwrapperexe |
Date: |
Wed, 9 Sep 2015 22:53:42 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 |
On 2015-09-09 17:07, Damian Bogel wrote:
> Hi,
>
> I'm using gnulib with mingw32 and I have a problem with redefines.
>
> At line 3657 @ build-aux/ltmain.in <http://ltmain.in>, commit
> 4ff16210c1089a3ba63a6f891442f0f1d8c20d96
>
> /* portability defines, excluding path handling macros */
> #if defined _MSC_VER
> # define setmode _setmode
> # define stat _stat
> # define chmod _chmod
> # define getcwd _getcwd
> # define putenv _putenv
> # define S_IXUSR _S_IEXEC
> #elif defined __MINGW32__
> # define setmode _setmode
> # define stat _stat
> # define chmod _chmod
> # define getcwd _getcwd
> # define putenv _putenv
> #elif defined __CYGWIN__
> # define HAVE_SETENV
> # define FOPEN_WB "wb"
> /* #elif defined other platforms ... */
> #endif
>
> This does not seem to take into consideration that gnulib might be used. I've
> been looking for a way to detect if gnulib is there or not, but couldn't find
> it. The only solution that comes to my mind is patching my libtool with
> #ifdef guards.
Hi!
Gnulib is not supposed to be involved when building the cwrapper, so
no, gnulib should not be considered here.
Is this perhaps the result of you patching in extra libs with sed when
linking the cwrapper, as you mention in bug #21445?
Cheers,
Peter