bug-gnu-libiconv
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gnu-libiconv] MSVC: 'invalid numeric argument'/Wl, -DLL, -IMPLI


From: Bruno Haible
Subject: Re: [bug-gnu-libiconv] MSVC: 'invalid numeric argument'/Wl, -DLL, -IMPLIB:.libs\charset.dll.lib''for builds on Windows
Date: Fri, 12 Jan 2018 19:09:07 +0100
User-agent: KMail/5.1.3 (Linux/4.4.0-104-generic; KDE/5.18.0; x86_64; ; )

Hi Alexander,

> I meant not to drop 'compile' use from libiconv builds using ICC on Windows 
> and MSVC (that's nearly impossible). I meant left the task to enable 
> 'compile' use for libiconv builds using ICC on Windows and MSVC to Autotools 
> (particularly Automake) itself via '_AM_PROG_CC_C_O' subroutine call. This 
> already done in 'configure' script, but not 'libcharset/configure' and 
> 'preload/configure' scripts.

The use of _AM_PROG_CC_C_O in the main 'configure' script
must be an unintended side-effect of using gnulib, I guess.

It does not make sense to invoke _AM_PROG_CC_C_O explicitly in
a configure.ac because
  * _AM_PROG_CC_C_O is not a documented Automake macro,
  * AM_PROG_CC_C_O is marked as obsolete in the documentation [1],
  * The README.windows states that special values need to be set for
    CC, CFLAGS, CXX, CXXFLAGS, CPPFLAGS, LD, NM, STRIP, AR, RANLIB,
    and AM_PROG_CC_C_O only helps for the value of CC.

> You misunderstood.

Indeed. Next time, please for a long mail, add a summary within the first
five lines of the mail; then I won't misunderstand :-)

Bruno

[1] https://www.gnu.org/software/automake/manual/html_node/Public-Macros.html




reply via email to

[Prev in Thread] Current Thread [Next in Thread]