Date: Wed, 10 Jan 2001 17:23:27 +0000 From: Ian Dowse <iedowse@maths.tcd.ie> To: "Robin P. Blanchard" <Robin_Blanchard@gactr.uga.edu> Cc: stable@freebsd.org, iedowse@maths.tcd.ie Subject: Re: buildworld over nfs failing consistently Message-ID: <200101101723.aa25474@salmon.maths.tcd.ie> In-Reply-To: Your message of "Wed, 10 Jan 2001 12:04:33 EST." <3A5C9621.1D8D74F@gactr.uga.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <3A5C9621.1D8D74F@gactr.uga.edu>, "Robin P. Blanchard" writes: >the only message was as originally posted: > >vm/vnode_pager.h -> vm/vnode_pager.ph >*** Error code 1 Sorry, I probably wasn't very clear. Before the first '*** Error code 1' message there will be a long list of 'xxx.h -> xxx.ph' messages, looking something like a.out.h -> a.out.ph aio.h -> aio.ph alias.h -> alias.ph ... cam/cam_ccb.h -> cam/cam_ccb.ph cam/cam_debug.h -> cam/cam_debug.ph ... vm/vm_zone.h -> vm/vm_zone.ph vm/vnode_pager.h -> vm/vnode_pager.ph (there are probably about 900 lines in this list altogether). Somewhere among this long list will be an error message, and the filename preceeding the error message will be the file that h2ph couldn't open. Ian >> Try looking carefully at the lines of output preceding the >> first '*** Error code 1' message. The 'h2ph' program will give out >> if it was unable to open any of the files in /usr/include that it >> tries to convert. I've seen an installworld fail because of this >> before. Among all the 'xxx.h -> xxx.ph' messages there should be >> something like: >> >> blah.h -> blah.ph >> Can't open blah.h: No such file or directory >> >> Usually when I've seen this, it is because of a dangling symlink >> on the machine where the installworld is being performed. >> >> Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi? <200101101723.aa25474>