From owner-freebsd-questions Thu Jan 29 04:47:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02105 for questions-outgoing; Thu, 29 Jan 1998 04:47:42 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from stcgate.statcan.ca (stcgate.statcan.ca [142.206.192.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA02099 for ; Thu, 29 Jan 1998 04:47:38 -0800 (PST) (envelope-from jeays@statcan.ca) Received: (from root@localhost) by stcgate.statcan.ca (8.6.11/8.6.9) id HAA23140 for ; Thu, 29 Jan 1998 07:51:04 -0500 Received: from stcinet.statcan.ca(142.206.128.146) by stcgate via smap (V1.3) id sma023132; Thu Jan 29 12:50:41 1998 Received: from statcan.ca by statcan.ca (SMI-8.6/SMI-SVR4) id HAA01288; Thu, 29 Jan 1998 07:49:20 -0500 Date: Thu, 29 Jan 1998 07:46:20 -0500 (EST) From: Mike Jeays X-Sender: jeays@austral To: freebsd-questions@FreeBSD.ORG Subject: Stable - compile error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" I grabbed the kernel source for -stable, and attempted to compile it on my 2.2.1 system. I got the following compile error: echo "___gnu_compiled_c" >>symbols.exclude grep -v '^#' ../../i386/i386/symbols.raw | sed 's/^ //' | sort -u > symbols.sort cc -c -x assembler-with-cpp -DLOCORE -nostdinc -I- -I. -I../.. -I/usr/include -DAPM_BROKEN_STATCLOCK -DAHC_FORCE_PIO -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DFFS -DINET -DKERNEL ../../i386/i386/locore.s ../../i386/i386/locore.s: Assembler messages: ../../i386/i386/locore.s:101: Error: Unknown pseudo-op: `.p2align' *** Error code 1 Stop. Is it feasible to run a kernel that is more up to date than the rest of the system, or must I do a complete upgrade? (I sort of have the feeling that this is a very naive question....) My objective is to try the ATAPI driver, which I understand can now support Iomega Zip drives, even if it is a bit buggy. Maybe I should wait for 2.2.6-RELEASE?