Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Oct 2007 13:03:59 -0400
From:      Robert Huff <roberthuff@rcn.com>
To:        Lionel Flandrin <simias.n@gmail.com>
Cc:        freebsd-current@freebsd.org
Subject:   fresh -CURRENT: ps: time: keyword not found
Message-ID:  <18214.4735.303373.626810@jerusalem.litteratus.org>
In-Reply-To: <86tzobzboe.fsf@simias.hd.free.fr>
References:  <86tzobzboe.fsf@simias.hd.free.fr>

next in thread | previous in thread | raw e-mail | index | archive | help
Lionel Flandrin writes:

>  On a -CURRENT csup'd a couple of hours ago, I get a message on
>  stderr every time in run "ps": "ps: time: keyword not found".

	I'm getting this too, on ps and a couple of other commands.
	I had thought this was related to a failed system update
(installworld broke; I thought I had sent a message but apparently
it didn't get here; message is repeated below).  Sorry to hear
there's a problem, good to know I'm not alone.


				Robert Huff

 ****************  repeated message	****************
	Yesterday (10/26 around 22:00 EDT) I updated source and went to
rebuild.
	Buildworld, buildkernel, installkernel all seem to have gone
fine.
	However, when I run installworld I get this:

===> sys/boot (install)
===> sys/boot/ficl (install)
===> sys/boot/efi (install)
===> sys/boot/efi/libefi (install)
===> sys/boot/i386 (install)
===> sys/boot/i386/mbr (install)
install  -o root -g wheel -m 444   mbr /boot
===> sys/boot/i386/pmbr (install)
install  -o root -g wheel -m 444   pmbr /boot
===> sys/boot/i386/boot0 (install)
install  -o root -g wheel -m 444   boot0 /boot
===> sys/boot/i386/boot0sio (install)
install  -o root -g wheel -m 444   boot0 /boot/boot0sio
===> sys/boot/i386/btx (install)
===> sys/boot/i386/btx/btx (install)
===> sys/boot/i386/btx/btxldr (install)
===> sys/boot/i386/btx/lib (install)
===> sys/boot/i386/boot2 (install)
cc -Os  -fno-guess-branch-probability  -fomit-frame-pointer  -fno-unit-at-a-time  -mno-align-long-strings  -mrtd  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3  -DUFS1_AND_UFS2  -DFLAGS=0x80  -DSIOPRT=0x3f8  -DSIOFMT=0x3  -DSIOSPD=9600  -I/usr/src/sys/boot/i386/boot2/../../common  -I/usr/src/sys/boot/i386/boot2/../btx/lib -I.  -Wall -Waggregate-return -Wbad-function-cast -Wcast-align  -Wmissing-declarations -Wmissing-prototypes -Wnested-externs  -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings  -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3  -S -o boot2.s.tmp /usr/src/sys/boot/i386/boot2/boot2.c
sed -e '/align/d' -e '/nop/d' < boot2.s.tmp > boot2.s
rm -f boot2.s.tmp
as  -o boot2.o boot2.s
ld -static -N --gc-sections -nostdlib -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o
objcopy -S -O binary boot2.out boot2.bin
btxld -v -E 0x2000 -f bin -b
/usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx
 -l boot2.ldr  -o boot2.ld -P 1 boot2.bin
btxld:No such file or directory
*** Error code 1

Stop in /usr/src/sys/boot/i386/boot2.
*** Error code 1

	If I got to the directory and run "make", everything seems to
work.
	Is anyone else seeing this?
	Is there anyway to find out which file btxld thinks is missing?
	(The system in question is at least semi-functional.  It boots,
and connects to the network; however, I would like to see a full
install cycle before opening it up again.)


					Robert Huff

				




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18214.4735.303373.626810>