lmi
[Top][All Lists]
Advanced

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

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


From: Vadim Zeitlin
Subject: Re: [lmi] pc-linux-gnu: wxPdfDoc configure fails
Date: Thu, 8 Oct 2020 17:42:26 +0200

On Thu, 8 Oct 2020 15:15:11 +0000 Greg Chicares <gchicares@sbcglobal.net> wrote:

GC> Vadim--I've almost built lmi's GUI for pc-linux-gnu, but I'm stuck
GC> on wxPdfDoc. The only lmi error is:
GC> 
GC> /opt/lmi/src/lmi/pdf_writer_wx.hpp:32:10: fatal error: wx/pdfdc.h: No such 
file or directory

 Well, it's the "only" error just because the build script didn't stop when
wxPdfDoc configure failed, as it should have...

GC> The output of 'install_wxpdfdoc.sh' contains:
GC> 
GC> configure: error: in 
`/opt/lmi/local/gcc_x86_64-pc-linux-gnu/wxpdfdoc-ad_hoc/wxpdfdoc-acbd019d18e991cca46a80e1be58e637774d5d3b':
GC> configure: error: wxWidgets required but not detected.
GC> See `config.log' for more details
GC> 
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
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.

 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.

VZ

Attachment: pgpAGctc8IMVR.pgp
Description: PGP signature


reply via email to

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