[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
  • Judd Montgomery judd at jpilot.org
    Sat Jun 10 12:24:07 EDT 2006

     

    Pedro Alves wrote:
    > 
    > Ok, I found it. There was not one single reference in Makefile to
    > install_user. Adding it manually it compiled successfully. Don't ask me why
    > configure didn't include it on the Makefile, my knowledge does not go that
    > far.
    > 
    > 
    Where are you getting this code you are building?  It does not seem to 
    be what is in CVS.  install_user is in the Makefile, UPGRADING has been 
    removed a while back.
    
    > The next error was in make install:
    > 
    > Making install in po
    > make[1]: Entering directory `/home/pedro/can2/jpilot/po'
    > /bin/sh .././mkinstalldirs /opt/jpilot-20050507//share
    > /bin/sh: .././mkinstalldirs: No such file or directory
    > make[1]: *** [install-data-yes] Error 127
    > make[1]: Leaving directory `/home/pedro/can2/jpilot/po'
    > make: *** [install-recursive] Error 1
    > 
    > 
    > Apparently mkinstalldirs should be there... but is not.
    > 
    You can get a copy of mkinstalldirs from somewhere on your system. 
    Usually there is one in the automake installation.  Its not in CVS, but 
    it does go in the released source tarball.
    
    Judd
    
    
    

     

     

    More information about the jpilot mailing list