Date: Sat, 3 May 1997 08:37:46 +0200 (MET DST) From: Wolfgang Helbig <helbig@MX.BA-Stuttgart.De> To: chaos@tgci.com Cc: questions@FreeBSD.ORG Subject: Re: (Fwd) Compiling custom kernal problems Message-ID: <199705030637.IAA01149@helbig.informatik.ba-stuttgart.de> In-Reply-To: <199705022346.QAA15507@train.tgci.com> from "Riley J. McIntire" at "May 2, 97 04:22:03 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, It looks like something went wrong during installation of the source tree. All error messages complain about broken stuff in /usr/src. This includes the compilation errors as well, since /usr/include/machine is sysmlinked to /usr/src/sys/i386/include. So why don't you try to reinstall the source with /stand/sysinstall? Running fsck(8) before that might be a good idea. Wolfgang > My security log output has a bunch of bad file descriptor messages > (sample below) which would seem to me to be the cause of my > kernal compile failure. > > A couple questions. File descriptors would seem to be low level file > system type objects intimately related to the partition/disk? > > And, would bad desciptors be an indication of a failing disk? (This > isn't the first time, but is definitely the worst I've seen.) > > This machine wasn't critical, but is about to become so. The disk is > a Maxtor IDE. 'Spose I oughta put a scsi in it, but still need to > know *if* it's the disk failing, or what? > > Again, thanks for the help. > > Cheers, > > Riley > > Partial output: > > find: /usr/src/gnu/usr.bin/cc/cc_int/version.c: Bad file descriptor > find: /usr/src/gnu/usr.bin/cc/cc_int/xcoffout.c: Bad file descriptor > find: /usr/src/gnu/usr.bin/perl/eg/sysvipc: Bad file descriptor find: > /usr/src/gnu/usr.bin/perl/x2p: Bad file descriptor find: > /usr/src/games: Bad file descriptor find: /usr/src/lib/csu: Bad file > descriptor find: /usr/src/lib/libc/db/man: Bad file descriptor find: > /usr/src/lib/libc/rpc: Bad file descriptor > > > > > > ------- Forwarded Message Follows ------- > From: Self <chaos> > To: questions@freebsd.org > Subject: Compiling custom kernal problems > Reply-to: chaos@tgci.com > Date: Thu, 1 May 1997 15:22:55 > > I'm trying to compile my first kernal in fbsd and getting some errors > that perhaps someone could help me with. > > > Here's the output: > > bash# make depend > errfil > In file included from /usr/include/ctype.h:51, > from ../../dev/aic7xxx/aic7xxx_asm.c:47: > /usr/include/runetype.h:42: machine/ansi.h: Not a directory > In file included from /usr/include/stdio.h:43, > from ../../dev/aic7xxx/aic7xxx_asm.c:48: > /usr/include/sys/types.h:48: machine/endian.h: Not a directory > /usr/include/sys/types.h:99: machine/ansi.h: Not a directory > /usr/include/sys/types.h:100: machine/types.h: Not a directory > In file included from ../../dev/aic7xxx/aic7xxx_asm.c:48: > /usr/include/stdio.h:48: machine/ansi.h: Not a directory > In file included from ../../dev/aic7xxx/aic7xxx_asm.c:49: > /usr/include/string.h:38: machine/ansi.h: Not a directory > In file included from ../../dev/aic7xxx/aic7xxx_asm.c:50: > /usr/include/stdlib.h:39: machine/ansi.h: Not a directory > > and errfil has this in it: > > cc -Wall -o aic7xxx_asm ../../dev/aic7xxx/aic7xxx_asm.c > *** Error code 1 > > I don't see any obvious (to me) problems with the config file, > attached. > > tia, > > Riley > > Attachments: > D:\tmp\CHARMED >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705030637.IAA01149>