[jp] Still unable to compile jpilot in slackware-current

  • Previous message: [jp] Still unable to compile jpilot in slackware-current
  • Next message: [jp] Still unable to compile jpilot in slackware-current
  • Pedro Alves pedro at neraka.no-ip.org
    Fri Jun 9 21:17:01 EDT 2006

     

    Hello
    
    On Fri, Jun 09, 2006 at 04:33:31PM -0700, TR wrote:
    > Hmm. [make] is trying to link [jpilot] using a version of install_user.o which 
    > doesn't appear to have compiled properly and thus is not providing the 
    > definition of install_user_gui().
    > 
    > Seems strange. I wonder whether a "make clean" and then a 'make' would help.
    
    No, it doesn't.
    
    > 
    > If I remember correctly, you were having trouble before with jpilot.c not 
    > compiling due to a nested function definition within a section of code 
    > surrounded by "ifdef __enable_gtk2". I thought the code looked kind of 
    > strange, and wasn't able to determine where the function's closing brace was. 
    > Anyway, I take it that removing "docs" handled this. Yes?
    > 
    
    
    Without removing docs, the error is:
    
    
    Making all in docs
    make[2]: Entering directory `/home/pedro/can2/jpilot/docs'
    make[2]: *** No rule to make target `../UPGRADING', needed by `all-am'.  Stop.
    make[2]: Leaving directory `/home/pedro/can2/jpilot/docs'
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory `/home/pedro/can2/jpilot'
    make: *** [all] Error 2
    
    
    I get the error with and without gtk2. I successfully compiled jpilot
    before, never had any problems at all. I cant identify what upgrade was
    responsable for this behaviour.  Maybe glibc, I have version 2.3.6
    
    
    -- 
    Pedro Alves
    
    

     

     

    More information about the jpilot mailing list