Re: Trouble with CVSUP to 4.0 Release, any ideas??
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' Yep; the problem can be fixed by doing 'make includes; make installworld' - it's caused by a dangling link (des.h) having nothing to point to at the time the perlification runs. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] 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 dead and not re-compiliable. :( The strange thing is I have been using CVS a long time, not like something new I am just trying to figure out here. All was fine up till a few weeks ago, and now if I cvsup an Alpha box I have here it's destroyed.. -Howard To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trouble with CVSUP to 4.0 Release, any ideas??
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 /usr/src/sys/ucontext.h Sure, here is it is: It does look reasonable. I'm suspicious about your compiler binaries - you might have to reinstall after all. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd.Phone: +44 181 442 9037 The strange part is that I have done this on two different Alpha machines, neither of which were more than a month behind on the CVS tree. I tried to update both to 4.0-RELEASE (RELENG_4 tag) and both are now in that state, so now I am totally afraid to even consider upgrading the other two to the release code. So whatever happened, was very easily reproduceable as I did it two times in a row. :( 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?? --- Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Trouble with CVSUP to 4.0 Release, any ideas??
rfile.c cd /usr/src/games/fortune/strfile; make _EXTRADEPEND echo strfile: /usr/obj/usr/src/alpha/usr/lib/libc.a .depend cc -O2 -pipe -Wall -I/usr/obj/usr/src/alpha/usr/include -c /usr/src/games/fortune/strfile/strfile.c In file included from /usr/src/games/fortune/strfile/strfile.c:56: /usr/include/stdlib.h:182: invalid #-line In file included from /usr/src/games/fortune/strfile/strfile.c:58, from /usr/src/games/fortune/strfile/strfile.c:56: /usr/include/string.h:98: invalid #-line *** Error code 1 Stop in /usr/src/games/fortune/strfile. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. As you can see they are dead, and I am at a loss as to why, but this happened exactly the same to two Alpha 164SX machine when I tried to go to RELEASE.. :( --- Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trouble with CVSUP to 4.0 Release, any ideas??
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 contents of /usr/src/sys/ucontext.h
Sure, here is it is:
u3$ cat ../../sys/ucontext.h
/*-
* Copyright (c) 1999 Marcel Moolenaar
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following disclaimer
*in this position and unchanged.
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in the
*documentation and/or other materials provided with the distribution.
* 3. The name of the author may not be used to endorse or promote products
*derived from this software without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
* IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
* IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*
* $FreeBSD: src/sys/sys/ucontext.h,v 1.4 1999/10/11 20:33:17 luoqi Exp $
*/
#ifndef _SYS_UCONTEXT_H_
#define _SYS_UCONTEXT_H_
#include machine/ucontext.h
typedef struct __ucontext {
/*
* Keep the order of the first two fields. Also,
* keep them the first two fields in the structure.
* This way we can have a union with struct
* sigcontext and ucontext_t. This allows us to
* support them both at the same time.
* note: the union is not defined, though.
*/
sigset_tuc_sigmask;
mcontext_t uc_mcontext;
struct __ucontext *uc_link;
stack_t uc_stack;
int __spare__[8];
} ucontext_t;
#endif /* !_SYS_UCONTEXT_H_ */
u3$
Looks normal enough to me.. :)
-Howard
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Buffer troubles, and machine hangs?
Hello, I am getting the following errors out of FreeBSD 4.0-CURRENT trying to run an IRC server, and was wondering if anyone had any ideas or recommended tunables I should set?? Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for [@163.152.216.46]:No buffer space available Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for [@208.164.193.201]:No buffer space available Mar 9 22:33:00 u syslogd: sendto: No buffer space available I have actually been fighting a problem with this machine locking up, and requiring a hard reset, and this is the only type errors I am actually seeing in the messages file. Not sure if this can cause such problems, so kind of grasping at straws to try and correct it. FYI, the IRC machine supports 4000+ clients connected at the same time, so if anyone has recommended tunables for this type of setup with so many active connections I would love to hear about it.. --- Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
