Hello, On 8/24/05, David Ayers <[EMAIL PROTECTED]> wrote: > Frederico Muñoz schrieb: > > Hello all, > > > > I have this problem lingering for some time now and I can't detect > > what causes it: whenever I do make install via sudo I get a "/bin/sh: > > pl2link: command not found" error message. I have found some messages > > with this problem in the archives but, alas, no answers. > > This is a security feature of your sudo configuration... (...) > Look at: > env |grep ^PATH > vs. > sudo env |grep ^PATH > and watch the GNUstep paths disappear. >
Yes, thanks. I was aware of the fact that the problem derived from the fact that the environment is reset by sudo, although I didn't make mention of it in my mail. What I found odd was that some applications (Gorm, fo example) work with "sudo make install". > Personally my inclination would be that we should try to avoid to run > any GNUstep tools during "make install" and have everything needed run > during make. But I'm not deep enough into -make to understand all the > implications to know if that's practical or not. For now I really > switch to root (which sets up by environment by sourcing GNUstep.sh) and > invoke "make install". > Yes, I'm doing the same, but this problem appeared due to the need of autobuilding Installer using a predifined set of methods that use make && sudo make install. I think that the pl2link invocation can indeed by done in "make", since all I see it do is creating a .desktop file in the application bundle. There is no need to be root for that. I'll try to change application.make and other relevant files to see if I can move pl2link somewhere else, since I think that "sudo make install" should work out of the box. Best Regards, fsmunoz _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev