On Thu, 16 Mar 2000, Andrew Gallatin wrote:
One thing to check would be: did your installworld acutally
complete? At one point the installworld was falling over in h2ph
when a crypto-related header file was being perl'ified. If this is
your problem, try doing a 'make -i installworld'
On Sat, 18 Mar 2000, Howard Leadmon wrote:
FYI, I tried both of the above, but still no solution. In fact I took a
fresh machine, loaded the last RC from 0307 to give me a pure
test bed in comparison to my other machines, and then did the
cvsup and buildworld and now that box is also
On Thu, 16 Mar 2000, Howard Leadmon wrote:
On Wed, 15 Mar 2000, Howard Leadmon wrote:
Any ideas how to fix this, or to get to 4.0 RELEASE on my other alphas do
I have to do a clean reload??
../../sys/ucontext.h:34: invalid #-line
../../alpha/alpha/genassym.c:44: #-lines for
Any ideas how to fix this, or to get to 4.0 RELEASE on my other alphas do
I have to do a clean reload??
../../sys/ucontext.h:34: invalid #-line
../../alpha/alpha/genassym.c:44: #-lines for entering and leaving files don't
match
Can I see the contents of
Howard Leadmon writes:
Has anyone updated a mid-febuary 4.0 to the RELEASE code on Alpha via CVS
and had it go smooth, and if so what steps did you use to get there??
Yes, at least 3. But my methods are rather unconventional. On my
build machine, which is running a 4.0-current box from
On Thu, 16 Mar 2000, Andrew Gallatin wrote:
One thing to check would be: did your installworld acutally
complete? At one point the installworld was falling over in h2ph
when a crypto-related header file was being perl'ified. If this is
your problem, try doing a 'make -i installworld'
Not really sure where to start, but here goes. I have several DEC PC164SX
machines running FreeBSD-Current, and my last cvsup was like Feb 28. While
I had the chance yesterday I decided to change my cvs tag to RELENG_4 and
bring things up to release. All seemed simple enough as I have
On Wed, 15 Mar 2000, Howard Leadmon wrote:
Any ideas how to fix this, or to get to 4.0 RELEASE on my other alphas do
I have to do a clean reload??
../../sys/ucontext.h:34: invalid #-line
../../alpha/alpha/genassym.c:44: #-lines for entering and leaving files don't match
Can I see the
On Wed, 15 Mar 2000, Howard Leadmon wrote:
Any ideas how to fix this, or to get to 4.0 RELEASE on my other alphas do
I have to do a clean reload??
../../sys/ucontext.h:34: invalid #-line
../../alpha/alpha/genassym.c:44: #-lines for entering and leaving files don't match
Can I see the