Re: [lmi] pc-linux-gnu: wxPdfDoc configure fails

[Greg Chicares]

On 2020-10-08 15:42, Vadim Zeitlin wrote:
> On Thu, 8 Oct 2020 15:15:11 +0000 Greg Chicares <gchicares@sbcglobal.net> 
> wrote:
[...]
> GC> and 'config.log' says:
> GC> 
> GC> configure:11670: checking for wx-config
> GC> configure:11689: found 
> /opt/lmi/local/gcc_x86_64-pc-linux-gnu/bin/wx-config
> GC> configure:11702: result: 
> /opt/lmi/local/gcc_x86_64-pc-linux-gnu/bin/wx-config
> GC> configure:11717: checking for wxWidgets version >= 2.8.0
> GC> configure:11838: result: no
> GC> 
> GC> However, when I run the 'wx-config' reported above at the command line
> GC> myself, it says I have 3.1:
> GC> 
> GC> $/opt/lmi/local/gcc_x86_64-pc-linux-gnu/bin/wx-config --release
> GC> 3.1
> GC> 
> GC> Any ideas?
> 
>  Not really. Configure code examines the output of "$WX_CONFIG --version"
> and judging from the error message it didn't get anything at all from it
> (otherwise it would have said "no (version x.y.z is not new enough)").
> However I don't see why wouldn't the command it uses, i.e.
> 
> /opt/lmi/local/gcc_x86_64-pc-linux-gnu/bin/wx-config --version 2>/dev/null
> 
> work. Could you please run it interactively just to check what happens? If

/opt/lmi/src/lmi[0]$/opt/lmi/local/gcc_x86_64-pc-linux-gnu/bin/wx-config 
--version 2>/dev/null
3.1.4

I assume that's close enough even though it's not exactly "3.1.5":

> it does return the expected "3.1.5" string, then I'm afraid my only idea is
> to put "set -x"/"set +x" around the configure lines indicates above (i.e.
> 11717 and 11838) and try to understand where do things go unexpectedly
> wrong.

Lines [11717, 11838] seem to pertain to something else, but I
added 'set -x' here (in a copy of 'configure' that I'll run manually:
  15747 
  15748 set -x
  15749     if test -x "$WX_CONFIG_NAME" ; then
  15750      { $as_echo "$as_me:${as_lineno-$LINENO}: checking for wx-config" 
>&5
and 'set +x' about a hundred lines later, and got:

+ printf '%s\n' 'configureXX:11718: checking for wxWidgets version >= 2.8.0'
+ printf %s 'checking for wxWidgets version >= 2.8.0... '
checking for wxWidgets version >= 2.8.0... + 
WX_CONFIG_WITH_ARGS='/opt/lmi/local/gcc_x86_64-pc-linux-gnu/bin/wx-config  
--exec-prefix=/opt/lmi/local/gcc_x86_64-pc-linux-gnu --prefix=/opt/lmi/local 
--host=x86_64-pc-linux-gnu '
++ /opt/lmi/local/gcc_x86_64-pc-linux-gnu/bin/wx-config 
--exec-prefix=/opt/lmi/local/gcc_x86_64-pc-linux-gnu --prefix=/opt/lmi/local 
--host=x86_64-pc-linux-gnu --version
+ WX_VERSION=

Copying the "++" command and executing it manually reproduces failure:

/opt/lmi/src/lmi[0]$/opt/lmi/local/gcc_x86_64-pc-linux-gnu/bin/wx-config 
--exec-prefix=/opt/lmi/local/gcc_x86_64-pc-linux-gnu --prefix=/opt/lmi/local 
--host=x86_64-pc-linux-gnu --version

          Warning: No config found to match: 
/opt/lmi/local/gcc_x86_64-pc-linux-gnu/bin/wx-config 
--exec-prefix=/opt/lmi/local/gcc_x86_64-pc-linux-gnu --prefix=/opt/lmi/local 
--host=x86_64-pc-linux-gnu --version
                   in /opt/lmi/local/gcc_x86_64-pc-linux-gnu/lib/wx/config
          If you require this configuration, please install the desired
          library build.  If this is part of an automated configuration
          test and no other errors occur, you may safely ignore it.
          You may use wx-config --list to see all configs available in
          the default prefix.

But if I remove all options except '--version', it succeeds:

/opt/lmi/src/lmi[1]$/opt/lmi/local/gcc_x86_64-pc-linux-gnu/bin/wx-config 
--version  
3.1.4

/opt/lmi/src/lmi[0]$wx-config --list
    Default config is gtk3-unicode-3.1
  Default config will be used for output

This gives a reproducible test case that depends only on 'wx-config'
and doesn't involve wxPdfDoc's 'configure' script.

Looking in the place suggested by the "Warning" above, I see:

/opt/lmi/src/lmi[0]$ls /opt/lmi/local/gcc_x86_64-pc-linux-gnu/lib/wx/config/*
/opt/lmi/local/gcc_x86_64-pc-linux-gnu/lib/wx/config/gtk3-unicode-3.1

which contains nothing that looks like an autoconf triplet in the
"leaf" component following the last '/' slash, whereas my working
i686-mingw build has a "leaf" containing a triplet:

/opt/lmi/src/lmi[0]$ls /opt/lmi/local/gcc_i686-w64-mingw32/lib/wx/config/*      
                  
/opt/lmi/local/gcc_i686-w64-mingw32/lib/wx/config/i686-w64-mingw32-msw-unicode-3.1

I'll say again that wxWidgets seemed to build correctly for pc-linux-gnu.
Perhaps I've just mislabeled its architecture somehow, so that I get
  ...wx/config/gtk3-unicode-3.1
where maybe
  ...wx/config/x86_64-pc-linux-gnu-gtk3-unicode-3.1
or something like that is needed?

>  Of course, an alternative could be to wait for a few more days until I
> finish my submodularization changes, as they should work both for cross-
> and normal compilation, but if you need it right now, I can only think of
> the above, sorry.

I don't want to distract you from that higher priority. I'm just hoping that
a quick glance will reveal to you some simple mistake I've made. Otherwise
I'll try brute force, which can be educational and does often work.