On Tue, 28 Jul 2015, Ken Stephens wrote:
> When I expect a variable to be in the environment and it isn't, I usually
> find that the application has shelled out of my environment and into
> anothers. This happens when I use root to install an application, which is
> usually required. Have your tried to add the variable into the root's
> environment?
Ken,
No, I haven't. In the application's source tree is a file with a method
that checks the installed wxPython version to ensure it's at least 2.8,9
preferably > 2.8.10. The two versions installed here (because another
application -- I forget which one -- won't run on 3.0.2.0 so 2.8.12.1 is
also installed).
Compilation (most application code is C, the GUI and accessories in
Python) always fails in the same module sub-directry, tplot. I specified the
wxPython version in both .py files in that subdirectory, in the method that
checks the installed version, in the configuration file (it didn't like that
at all; won't complete configuring), and in my shell (which is used to
configure and build the application).
So, since all of the above keep failing when tplot is being built (almost
10 minutes in a 12-minute build) it seems reasonable that the application is
seeing both wxPython versions, ignoring version.select('3.0.2.0'), and
halting when it cannot figure out which one to use ... on this one module
after successfully building other Python modules.
Time for me to contact the project's lead dev; I think I know who develops
that one module but I'm not sure so I'll ask him to put someone on the
problem. I was involved in its development until about 10 years ago so I
know most of the folks quite well.
Thanks for the suggestion,
Rich
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
