On Thursday 19 September 2002 14:56, Erik Jakobsen wrote: > Hi. > > I saw the nice software checkinstall, and would having it installed. > > Here is the first results. > > eurit:/home/erik/check/usr/local/sbin # ./checkinstall ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Thats your problem, run ./checkinstall in its source directory. As far as i am concerned i will stick to what i wrote yesterday about using /usr/local/* for software that i install, i know then where to look. I find it misleading when one issues a normal nix command and gets confronted with what Erik got, BUT we all know what the old saying is dont we, "RTFM" even if the README is 21740 bytes long. Other than that it seems a handy program for those who want something to do for them that they can really do themselfs. > > checkinstall 1.5.3, Copyright 2001 Felipe Eduardo Sanchez Diaz Duran > This software is released under the GNU GPL. > > > The package documentation directory ./doc-pak does not exist. > Should I create a default set of package docs? [y]: y > > Preparing package documentation...OK > > *** No known documentation files were found. The new package > *** won't include a documentation directory. > > Installing with "make install"... > > ========================= Installation results =========================== > make: *** No rule to make target `install'. Stop. > > **** Installation failed. Aborting package creation. > > Cleaning up...OK > > Bye. > > What is to be done now ?. Read the manual ?. -- Regards Richard [EMAIL PROTECTED] http://people.zeelandnet.nl/pa3gcu/ - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
