I'm not really sure I understand 100% of the issue here.
On Sun, Nov 2, 2008 at 10:26 PM, Michael D. Setzer II <[EMAIL PROTECTED]> wrote: > I have the g4l project that uses busybox plus a number of other programs. > A number of the additional programs I was building and installing manually > into directories in > the path. Into what path? >As it turns out, some of the programs make install puts the files in the >/usr/local/bin > or /usr/local/sbin. > > I then wrote a little script that will compare the files in my build > directory, to the systems to > see if the files have been updated, and show what is different. I then moved > the files from > there old locations to the new /usr/local directories. I had found a web page > saying the > /usr/local directories are part of the standard path. But a test of the new > build fail, and > checking the path showed the /usr/local were not part of the path with the > boot. > When you do a "make install" you should do something like "make DESTDIR=<path-root-of-install> install". That's if I understand what you wrote above. I do this for many applications that I build and put into my ramdisk. > I added an export to command to the .bash_profile to fix the issue, but was > wondering if there > is a better way, or if this is how things are suppose to be. Not sure where > the PATH value is > set. > Yeah.. this is where I'm tossed off. Adding an export command for what? Anyway.. I hope my little bit of info above helped. -stv -- /* * Steve Iribarne * Software Engineer * (aka Grunt) */ _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
