Re: buildworld/installworld problem
Go back to your original scheme. Make knows what the true path was when you did the build and it has to look like that on the clients. If you link /array/src as /usr/src, make knows it was really /array/src. You would have to nfs_mount /array/src and link it to /usr/src. Why do that when you could have created a partition on the array slice called src and mounted it as /usr/src. Then, you could nfs_mount that partition as /usr/src and everything is happy. true - but i wanted a single machine to handle doing builds of -stable and -release as i have machines with different needs. if this is impossible then i'll settle, i just figured there was some flag i could possibly pass to the make installworld to fix the problem. thanks for the reply, -randall -- :// randall s. ehren :// voice 805.893.5632 :// systems administrator:// isber|survey|avss.ucsb.edu :// institute for social, behavioral, and economic research To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: buildworld/installworld problem
On Tuesday 14 January 2003 12:04 am, randall ehren wrote: Go back to your original scheme. Make knows what the true path was when you did the build and it has to look like that on the clients. If you link /array/src as /usr/src, make knows it was really /array/src. You would have to nfs_mount /array/src and link it to /usr/src. Why do that when you could have created a partition on the array slice called src and mounted it as /usr/src. Then, you could nfs_mount that partition as /usr/src and everything is happy. true - but i wanted a single machine to handle doing builds of -stable and -release as i have machines with different needs. if this is impossible then i'll settle, i just figured there was some flag i could possibly pass to the make installworld to fix the problem. There are some env parameters that you can change but I couldn't find them. I do my builds on my fastest system and want them done as quickly as possible. So, I have /usr/src and /usr/obj on their own HD/controller. Your answer should be in the archive. Look around DESTDIR and others. Then, don't bother doing the link to /usr/src and /usr/obj. It doesn't matter at that point. That doesn't get you around the fact that make builds files with the original path built in. Kent thanks for the reply, -randall -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
buildworld/installworld problem
hi, i have a machine that i use for building freebsd for a bunch of other machines. in my old setup, all worked well, but now i am experiencing a few problems which seem related to symlinking and mount points. in the old setup /usr/src /usr/obj were just your typical partitions on a single disk, as in: /dev/da0s1g/usr/src /dev/da0s1h/usr/obj in the new setup /usr/src /usr/obj are on the same partition, symlinked as follows: /dev/ccd0c /array /usr/src -- /array/src /usr/obj -- /array/obj on this machine, make buildworld works fine. installworld works just as well. however, when i go to do a make installworld on a client (having mounted /usr/src /usr/obj via NFS) it dies right here: echo \#'define __FreeBSD_version' $RELDATE osreldate.h; echo #endif osreldate.h touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 now if i do the following: % ln -s /usr/obj/array /usr/obj/usr then run make installworld again, all is well until it gets to: ln -s /usr/src/lib/libncurses/../../contrib/ncurses/man/curs_addch.3x curs_addch.3 ln: curs_addch.3: File exists *** Error code 1 Stop in /usr/src/lib/libncurses. *** Error code 1 after searching on google for that error, it turns up that i can use the -k flag with make. if i then run make -k installworld it spits up many errors (all related to ncurses) but completes the install. ideally i would like to have this machine build -stable -release as we have client machines of different needs, so i envisioned having a nice ccd raid-0 of disks to hold the builds. any ideas? thanks. -- :// randall s. ehren :// voice 805.893.5632 :// systems administrator:// isber|survey|avss.ucsb.edu :// institute for social, behavioral, and economic research To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: buildworld/installworld problem
On Monday 13 January 2003 07:17 pm, randall ehren wrote: hi, i have a machine that i use for building freebsd for a bunch of other machines. in my old setup, all worked well, but now i am experiencing a few problems which seem related to symlinking and mount points. in the old setup /usr/src /usr/obj were just your typical partitions on a single disk, as in: /dev/da0s1g /usr/src /dev/da0s1h /usr/obj in the new setup /usr/src /usr/obj are on the same partition, symlinked as follows: /dev/ccd0c /array /usr/src -- /array/src /usr/obj -- /array/obj on this machine, make buildworld works fine. installworld works just as well. however, when i go to do a make installworld on a client (having mounted /usr/src /usr/obj via NFS) it dies right here: echo \#'define __FreeBSD_version' $RELDATE osreldate.h; echo #endif osreldate.h touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 now if i do the following: % ln -s /usr/obj/array /usr/obj/usr then run make installworld again, all is well until it gets to: ln -s /usr/src/lib/libncurses/../../contrib/ncurses/man/curs_addch.3x curs_addch.3 ln: curs_addch.3: File exists *** Error code 1 Stop in /usr/src/lib/libncurses. *** Error code 1 after searching on google for that error, it turns up that i can use the -k flag with make. if i then run make -k installworld it spits up many errors (all related to ncurses) but completes the install. ideally i would like to have this machine build -stable -release as we have client machines of different needs, so i envisioned having a nice ccd raid-0 of disks to hold the builds. any ideas? thanks. Go back to your original scheme. Make knows what the true path was when you did the build and it has to look like that on the clients. If you link /array/src as /usr/src, make knows it was really /array/src. You would have to nfs_mount /array/src and link it to /usr/src. Why do that when you could have created a partition on the array slice called src and mounted it as /usr/src. Then, you could nfs_mount that partition as /usr/src and everything is happy. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
