cvs commit: src/sys/sys gpt.h src/lib/libstand Makefile
src/sbin/gpt Makefile add.c boot.c gpt.8 gpt.c gpt.h show.c
src/sys/boot/common ufsread.c src/sys/boot/i386 Makefile
src/sys/boot/i386/gptboot Makefile gptboot.c gptldr.S ...
jhb at freebsd.org
Sat Oct 27 15:12:35 PDT 2007
On Saturday 27 October 2007 02:45:42 pm Robert Watson wrote:
> On Sat, 27 Oct 2007, John Baldwin wrote:
> >> /usr/obj/usr/src/sys/boot/i386/gptboot/../btx/btx/btx -l gptldr.bin -o
> >> gptboot gptboot.bin btxld:No such file or directory *** Error code 1
> >> Stop in /usr/src/sys/boot/i386/gptboot. *** Error code 1
> > Hmm, this is probably the classic problem of the machine symlink being a
> > newer date than the build causing installworld to try and rebuild the binary
> > when it shouldn't. I've seen this on boot2 when storing the output of a
> > buildworld in a cpio and extracting it since cpio doesn't preserve the times
> > on symlinks. We actually just comment out the dependency on the 'machine'
> > symlinks at work since we use cpio. :-/
> Indeed -- it turned out that time in my Parallels VM had mysteriously
> regressed four days (or failed to leap forward four days?). ntpdate, blowing
> away /usr/obj and touching /usr/src followed by a rebuild did the trick.
> Sorry about the false alarm.
No problem, glad it is ok now.
More information about the cvs-all