[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Sunday 06 February 2005 10:43 pm, Grant Sewell wrote:
On Sun, 06 Feb 2005 19:28:03 +0000 Julian Hall wrote:Neil, Robin, thanks guys the FAT32 was most of the problem. However, I just tried to compile the latest CUPS 5.0.0 Beta2, the make worked, make install didn't. This was logged in (as you can see) as me. Should I try this as root?Yes. There are (to my knowledge) very few things that are designed to be "make install"ed as a normal user.
Only if you accept the defaults, Grant. If you need/want to install in a home directory or in /opt/, all you generally need is --prefix. Note however that a lot of packages are moving to ./autogen.sh which does some pre-configure configuration and then calls ./configure with specialised arguments. Don't assume ./configure will be there. Passing arguments to ./autogen.sh will get those passed on to the nested ./configure but there's no substitute for reading the README and README.cvs where provided. If those don't answer the question, ask (nicely) before leaping in where angels fear to tread. :-) It's not the design of the package itself that requires the root user to make install - it is solely down to the permissions of the default directories. /opt/ is often root user only or similar, changing that is very useful and provides a great place for all these types of builds.
Of course it actually has more to do with directory permissions, etc, but it's normally easier to simply "su" on a single-user system.
Precisely. If you expect the code to work at the system level, you will need su. You would be very unwise to allow installation of anything that is accessible system-wide without the root password. -- Neil Williams ============= http://www.dcglug.org.uk/ http://www.nosoftwarepatents.com/ http://sourceforge.net/projects/isbnsearch/ http://www.neil.williamsleesmill.me.uk/ http://www.biglumber.com/x/web?qs=0x8801094A28BCB3E3
Attachment:
pgp00010.pgp
Description: PGP signature