make world dying
I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT unsuccessfully. It used to die in perl, then that was fixed, but for the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386. Is this a known problem? Yes, I'm a CURRENT newbie, but hopefully only until the split to 3.1 when I can hopefully then play with 3.1-STABLE. Are questions such as the above better addressed to -questions or -current? Thanks. Hoping to catch a cvsup when the source tree will build, Aaron out. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make world dying
Hmmm, I zapped my /usr/obj clean around 1100PST 19/Jan/1999 and made world just fine. Try starting with an empty /usr/obj. You can pretty much glean from reading -current whether or not most people are building it or if it is broken. -questions is more for general freebsd issues. -Chris On Tue, 19 Jan 1999, Aaron D. Gifford wrote: I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT unsuccessfully. It used to die in perl, then that was fixed, but for the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386. Is this a known problem? Yes, I'm a CURRENT newbie, but hopefully only until the split to 3.1 when I can hopefully then play with 3.1-STABLE. Are questions such as the above better addressed to -questions or -current? Thanks. Hoping to catch a cvsup when the source tree will build, Aaron out. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make world dying
:Hmmm, I zapped my /usr/obj clean around 1100PST 19/Jan/1999 and made world :just fine. Try starting with an empty /usr/obj. : :You can pretty much glean from reading -current whether or not most people :are building it or if it is broken. -questions is more for general :freebsd issues. : :-Chris : :On Tue, 19 Jan 1999, Aaron D. Gifford wrote: : : I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT : unsuccessfully. It used to die in perl, then that was fixed, but for :... I updated my tree last night and was able to do a buildworld without mishap, but I already had a mostly -current install. However, I do not recall there being a specific problem with libi386. The only other thing I can think of is that I'm doing an ELF build, and I suppose it is possible that the A.OUT build is broken and the ELF build is not. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make world dying
Aaron D. Gifford wrote: I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT unsuccessfully. It used to die in perl, then that was fixed, but for the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386. Is this a known problem? Yes, I'm a CURRENT newbie, but hopefully only until the split to 3.1 when I can hopefully then play with 3.1-STABLE. A good plan is to include the actual diagnostic, together with some context, if you run into a problem. For instance: | /usr/obj/elf/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o | boot2.ld -P 1 boot2.bin | kernel: ver=0.87 size=6d0 load=9000 entry=9010 map=16M pgctl=1:1 | client: fmt=bin size=143c text=0 data=0 bss=0 entry=0 | output: fmt=bin size=1d0c text=200 data=1b0c org=0 entry=0 | 244 bytes available | dd if=boot2.ld of=boot2 obs=7680 conv=osync 2/dev/null | === sys/boot/i386/libi386 | make: don't know how to make machine/ansi.h. Stop | *** Error code 2 | | Stop. That way, if it's not a known problem, but some form of pilot error, you may get some useful help anyway. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
