amd broken
This commit breaks the build of amd: obrien 2001/09/05 09:54:21 PDT Modified files: usr.sbin/amd Makefile.inc usr.sbin/amd/include newvers.sh Log: Try to determine the OS version and architecture for what is being built vs. the building machine. PR: 14040 Revision ChangesPath 1.8 +4 -1 src/usr.sbin/amd/Makefile.inc 1.4 +17 -10src/usr.sbin/amd/include/newvers.sh This is because of +if [ -e ../../../sys/conf/newvers.sh ]; then in newvers.sh It happens to work if I build amd in /usr/src. If I have /usr/obj/... the Makefile is executed in the object directory, so that the path is wrong. The 'else' part of the above fails to generate the HOST_OS_VERSION, and this makes the build to fail. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: amd broken
On Thu, Sep 06, 2001 at 04:58:28PM +0200, Harti Brandt wrote: It happens to work if I build amd in /usr/src. If I have /usr/obj/... You can guess how I tested it... ;-) My reference box's build failed last night in libc. I'm updating it now so I can fix this. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: AMD broken in -current?
On Thu, Oct 26, 2000 at 09:04:45PM -0700, Jordan Hubbard wrote: It use to work in early October, but now I get the following using the stock (/etc/defaults/rc.conf) amd flags: It works on my Oct 22nd world. OK, so maybe it broke even later. What does it do on your Oct 27th world? :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AMD broken in -current?
On Fri, Oct 27, 2000 at 09:34:07AM -0700, Jordan Hubbard wrote: On Thu, Oct 26, 2000 at 09:04:45PM -0700, Jordan Hubbard wrote: It use to work in early October, but now I get the following using the stock (/etc/defaults/rc.conf) amd flags: It works on my Oct 22nd world. OK, so maybe it broke even later. What does it do on your Oct 27th world? :) On a 4.5hr old world (I need more sleep), it also works fine. -- David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
AMD broken in -current?
It use to work in early October, but now I get the following using the stock (/etc/defaults/rc.conf) amd flags: amd[321]: /host: mount: Operation not supported by device amd[322]: /net: mount: Operation not supported by device amd[321]: /host: mount: No such file or directory amd[322]: /net: mount: No such file or directory amd[321]: extra mkdirs required for /host amd[321]: mount_amfs_toplvl: Operation not supported by device amd[322]: extra mkdirs required for /net amd[322]: mount_amfs_toplvl: Operation not supported by device amd[320]: /host: mount (amfs_auto_cont): Operation not supported by device amd[320]: /net: mount (amfs_auto_cont): Operation not supported by device After which amd continues to run but is essentially useless since it has no hooks into the filesystem. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AMD broken in -current?
On Thu, Oct 26, 2000 at 09:04:45PM -0700, Jordan Hubbard wrote: It use to work in early October, but now I get the following using the stock (/etc/defaults/rc.conf) amd flags: It works on my Oct 22nd world. -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
