[jp] Fixing A Broken Jpilot Installation

  • Previous message: [jp] Fixing A Broken Jpilot Installation
  • Next message: [jp] Fixing A Broken Jpilot Installation
  • Rich Shepard rshepard at appl-ecosys.com
    Mon Aug 7 14:06:47 EDT 2006

     

    On Mon, 7 Aug 2006, David A. Desrosiers wrote:
    
    > 	Try building it from source with debug symbols (not CVS, but the
    > same source rpm or tarball which matches your failing version), and then
    > run it through gdb and get a backtrace.
    
    David,
    
       I don't see an option in ./configure to turn on debugging. However, when I
    try './configure --enable-gtk2' this is the result:
    
    checking for GTK+ - version >= 2.0.3... no
    *** Could not run GTK+ test program, checking why...
    *** The test program failed to compile or link. See the file config.log for
    the
    *** exact error that occured. This usually means GTK+ is incorrectly
    installed.
    configure: error: *** GTK >= 2.0.3 not found ***
    
       However, gtk+2-2.8.12 _is_ installed.
    
       Without the gtk+2 support, it configures and builds ... and runs! But, not
    with any of my records. Sigh.
    
       What is going on here? Guess I'll wait for Judd to have some time to look
    at this.
    
    Rich
    
    -- 
    Richard B. Shepard, Ph.D.               |    The Environmental Permitting
    Applied Ecosystem Services, Inc.(TM)    |            Accelerator
    <http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863
    
    

     

     

    More information about the jpilot mailing list