Re: [lmi] [Bulk] Re: Cross-compiling lmi from Linux to MSW

[Greg Chicares]

On 2016-01-22 19:35, Vadim Zeitlin wrote:
> On Fri, 22 Jan 2016 17:49:02 +0000 Greg Chicares <address@hidden> wrote:
[...debian-7, MinGW-w64 gcc-4.6 ...]
> GC> error: invoking macro WX_DEFINE_SORTED_USER_EXPORTED_TYPEARRAY argument
> GC> 4: empty macro arguments are undefined in ISO C90 and ISO C++98
> 
>  I could look at this if you'd like, but I think switching to 4.9 is a
> better idea.

Okay, I've been making progress with 4.9.1 on debian-8 (fully updated).
I've gone over all the dependencies carefully, and I think they've all
been built successfully. The problem now is lmi; the attachment is the
output from a final run of 'make install', after several preceding
runs built everything that succeeded; now it's down to linker errors.

First of all [not in attachment because this command succeeded]:
    CXX    liblmi_la-authenticity.lo
'make' output from some other autotoolized packages shows actual commands;
is there a way to see the same thing here? When a command fails, I like to
paste it into a terminal and experiment with it, to find out exactly what's
going on.

That would help here:

  CXXLD    lmi_cli.exe
libtool: link: Could not determine the host path corresponding to
libtool: link:   `/home/greg/msw/i686-w64-mingw32/lib'
libtool: link: Continuing, but uninstalled executables may not work.
libtool: link: Could not determine the host path corresponding to
libtool: link:   
`/home/greg/msw/i686-w64-mingw32/lib:/home/greg/msw/i686-w64-mingw32/bin'
libtool: link: Continuing, but uninstalled executables may not work.
./.libs/lt-lmi_cli.c:39:5: error: '_putenv' redeclared without dllimport 
attribute: previous dllimport ignored [-Werror=attributes]
 int _putenv (const char *);
     ^
I don't know exactly what it's trying to do, so it's hard to debug.
AFAICT, the "Could not determine the host path" part is innocuous.
But where does the '_putenv' warning come from? I don't find any
'_putenv' call in lmi, which doesn't have any 'lt-lmi_cli.c' file
(and has very few '.c' files at all). Is libtool actually writing
a C program to invoke the linker? and if so, since it's a linux
libtool, how could it write a C program with a 'dllimport' error?

I consulted the Source of All Knowledge:
  
https://www.google.com/search?q=error%3A+'_putenv'+redeclared+without+dllimport+attribute
and...oh, no!...the first result is a message from you:
  https://lists.gnu.org/archive/html/libtool/2011-06/msg00037.html
And you're talking about a project that still used gcc-3.4.5 in 2011,
and insists on using '-Werror'. (I bet it uses '-pedantic', too.)
Then the only response you get is from yourself. Should I now look
for your patch and apply it?

BTW, changing the subject, I configured thus:

PATH=$HOME/msw/i686-w64-mingw32/bin:$PATH ~/src/lmi/configure \
  --prefix=$HOME/msw/i686-w64-mingw32 --host=i686-w64-mingw32 \
  CPPFLAGS=-I$HOME/msw/i686-w64-mingw32/include \
  LDFLAGS=-L$HOME/msw/i686-w64-mingw32/lib \
  CXXFLAGS='-Wno-unused-local-typedefs -Wno-unused-variable' 2>&1 |less

so to get C++11 am I supposed to add '-std=c++11' to CXXFLAGS?
If so, should I do that to every 'configure' command and then
rebuild every library (except libxml2 and libxslt, which are
just plain C)?

lmi-build-log
Description: Text document