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

[Greg Chicares]

On 2016-01-25 03:14, Greg Chicares wrote:
> On 2016-01-23 15:40, Vadim Zeitlin wrote:
> [...]
>>  Yes, please see https://savannah.gnu.org/patch/?8843
> 
> /home/greg/build/lmi-msw[0]$whence ltmain.m4sh
> /home/greg/build/lmi-msw[1]$whence libtool
> /usr/bin/libtool
> /home/greg/build/lmi-msw[0]$ls /usr/bin/libtool/**/ltmain.m4sh
> zsh: no matches found: /usr/bin/libtool/**/ltmain.m4sh
> /home/greg/build/lmi-msw[1]$ls /usr/**/libtldl
> zsh: no matches found: /usr/**/libtldl

ell-tee, not tee-ell:
  ls /usr/**/libltdl

However:

/usr/share/libtool/config[0]$ls **/ltmain.m4sh
zsh: no matches found: **/ltmain.m4sh
/usr/share/libtool/config[1]$ls
compile  config.guess  config.sub  depcomp  install-sh  ltmain.sh  missing

No 'ltmain.m4sh'; is 'ltmain.sh' the same thing? (I find no 'ltmain.m4sh'
on either debian-7 or debian-8.)

/usr/share/libtool/config[0]$grep -A3 MINGW ltmain.sh
#if defined(__MINGW32__)
# ifdef __STRICT_ANSI__
int _putenv (const char *);
# endif

So I just patch that manually, right? And I don't have to worry too much
about altering an important file in /usr/share/ because, well, it's a
frank error? But as soon as I upgrade, my local patch will vanish and
I'll be back in a world of hurt?