Follow-up Comment #5, bug #26437 (project gnustep): Yes, this is not a gnustep-base problem.
In fact, it's not even a GNUstep problem :-). You'll have the same problem with any other software that is installed into a custom, non-native location. Eg, if you install some package into /opt/package, you then obviously have to add /opt/package/bin (or whatever it is) to your PATH before you can use it properly. And if you're using 'sudo' to do stuff (an almost identical example is Python's "sudo setup.py install" if you have your own custom Python installation), then you need to make sure /opt/package/bin is in root's PATH as well ;-) I can see two solutions: * install gnustep-make "properly" so that root can use it (either by installing it using a native filesystem so that gnustep-config automatically ends up in the PATH, or if it's installed in a non-native setup, by adding the gnustep paths to the PATH and LD_LIBRARY_PATH in /etc/profile or similar) * use 'sudo -E make install' so that root will inherit the 'temporary' environment from your current user. I agree with Richard that the best thing we can do is to improve the documentation. The error message printed by gnustep-base when gnustep-make can't be found is a good place to put any helpful explanation as that is most likely where users would stumble upon this problem. :-) I agree with closing the bug as I am not sure what more we could do. ;-) Thanks _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?26437> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep