From owner-freebsd-current Sun Dec 31 21:09:23 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA08269 for current-outgoing; Sun, 31 Dec 1995 21:09:23 -0800 (PST) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA08251 Sun, 31 Dec 1995 21:09:16 -0800 (PST) Received: from spunky.vpm.com ([205.162.123.143]) by mail.barrnet.net (8.7.1/MAIL-RELAY-LEN) with SMTP id XAA04524; Mon, 25 Dec 1995 23:57:53 -0800 (PST) Received: (from root@localhost) by spunky.vpm.com (8.6.12/8.6.12) id XAA06775; Mon, 25 Dec 1995 23:56:23 GMT From: Mark Stout Message-Id: <199512252356.XAA06775@spunky.vpm.com> Subject: Re: Missing File in sys/i386/include/conf.h ? To: questions@freebsd.org Date: Mon, 25 Dec 1995 23:56:23 +0000 () Cc: current@freebsd.org In-Reply-To: from "James FitzGibbon" at Dec 23, 95 01:50:47 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Well, I must be dense or something, but I can't get -current to create the damn ioconf.h file for the life of me. I don't know what changed from 2.1r that would cause it to bomb. But it does. I've followed this thread which has provided me no information that I didn't already know or do. I get the following error right after the deletion of the old compiled directory. I don't know why it's unknown, especially when it's like the third one down in a list of 5. No modifications of the makefile has been done, option options selected, and later commected out in hopes of getting it to compile, which hasn't helped. I'm not a Unix programmer, but under- stand most of what's going on without needing to know the mechanics. Unknown % construct in generic makefile: %SFILES Why does this show up and how can I eliminate it. What files does -current need to have in order to compile correctly? If I had sup setup, would I be experiencing this problem? If sup IS setup, will I be downloading code that could break my system, which is a production box? I don't want to beta new code. I need help. I *need* BSDI 2.0 binary compatibility and it's been like pulling teeth with tweezers to get a working compilable kernel. I'm just a tad bit frustrated at this whole process because I"ve wasted alot of time dinking around trying to figure out why the damn won't compile. All the great advice so far hasn't helped. I've downloaded the entire directory structure of /.3/FreeBSD/FreeBSD-current/src/ from ftp.cdrom.com so unless there's more I should have all the code. What else do I need to do? I'm running 2.1R now without problems and the compilation went very smooth. iocomf.h must have been created when I compiled that version. I have removed any additions to the new kernel and basically have the same kerenl config as that of 2.1R. I have to be missing something other that just rerunning config . I can't believe that this is that hard to get straight. Besides compiling the new kernel, what else will I need to compile in order to get -current to work. I don't have a second machine to work with so what ever I do has to be done on a production box and then rebooted. I'd like a second box, but I have to wait on that. Thanks for letting me get my frustrations out. 5 days is too long to be dinking with this thing. Mark ========================================================================== Mark Stout | The Village Potpourri Mall: http://www.vpm.com/ -------------+----------------------------------------------------------- VPM Enterprises; P.O.Box 6427; Folsom, CA 95763-6427 Secured Internet Sales, Marketing and Advertising Specialist ==========================================================================