From owner-freebsd-current  Mon Feb  5 12:44:50 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA22341
          for current-outgoing; Mon, 5 Feb 1996 12:44:50 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA22336
          for <current@FreeBSD.org>; Mon, 5 Feb 1996 12:44:46 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA15814; Mon, 5 Feb 1996 13:41:22 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199602052041.NAA15814@phaeton.artisoft.com>
Subject: Re: -current build problems
To: root@fw.ast.com (The Amazing Big Guy)
Date: Mon, 5 Feb 1996 13:41:21 -0700 (MST)
Cc: current@FreeBSD.org, kent@fw.ast.com
In-Reply-To: <m0tjIRg-000858C@fw.ast.com> from "The Amazing Big Guy" at Feb 4, 96 10:22:00 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.org
Precedence: bulk

> >cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit
>  -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes  -Winline
>  -nostdinc -I. -I../.. -I../../sys -I../../../include -DGENERIC -DI686_CPU
>  -DI586_CPU -DI486_CPU -DI386_CPU -DATAPI -DUCONSOLE -DBOUNCE_BUFFERS
>  -DSCSI_DELAY="15" -DCOMPAT_43 -DPROCFS -DCD9660 -DMSDOSFS -DNFS -DFFS
>  -DINET -DMATH_EMULATE -DKERNEL -DTIMEZONE=0 -DDST=0 -DMAXUSERS=10
>  -UKERNEL ../../i386/i386/genassym.c
> >../../i386/i386/genassym.c:40: opt_sysvipc.h: No such file or directory
> >*** Error code 1
> >Stop.
> 
> Any ideas?  "find" cannot locate "opt_sysvipc.h" anywhere in the -current
> tree.

I just had this same problem, after telling someone to update their config
after they had the same problem.

My problem was that I still had an old config.

It seems my usr.sbin sup pointer was incorrect since I changed to the
new SUP server and so my sources had not been updated.


So: update your config, build it, install it, config a new kernel,
and then be happy.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.