From: David van Hoose <davidvh@cox.net>
To: linux-kernel@vger.kernel.org
Subject: Kenel compilation failure
Date: Sat, 07 Dec 2002 16:02:21 -0600 [thread overview]
Message-ID: <3DF26FED.5070502@cox.net> (raw)
I downloaded kernel 2.4.20 and got the following during 'make modules'
; SNIP
gcc -D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer
-pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DMODVERSIONS
-include /usr/src/linux-2.4.20/include/linux/modversions.h -nostdinc
-iwithprefix include -DKBUILD_BASENAME=scsi_syms -DEXPORT_SYMTAB -c
scsi_syms.c
ld -m elf_i386 -r -o scsi_mod.o scsi.o hosts.o scsi_ioctl.o constants.o
scsicam.o scsi_proc.o scsi_error.o scsi_obsolete.o scsi_queue.o scsi_lib.o
scsi_merge.o
scsi_dma.o scsi_scan.o scsi_syms.o
ln -sf sim710.scr fake7.c
gcc -E -D__KERNEL__ -I/usr/src/linux-2.4.20/include -traditional
-DCHIP=710 fake7.c | grep -v '^#' | perl -s script_asm.pl -ncr710
script_asm.pl : Illegal combination of registers in line 72 : MOVE
CTEST7 & 0xef TO CTEST7
Either source and destination registers must be the same,
or either source or destination register must be SFBR.
make[2]: *** [sim710_d.h] Error 255
make[2]: Leaving directory `/usr/src/linux-2.4.20/drivers/scsi'
make[1]: *** [_modsubdir_scsi] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.20/drivers'
make: *** [_mod_drivers] Error 2
; SNIP
I didn't know who exactly to send that to, but I am definately sure that
isn't supposed to happen. I've attached my configuration file to help.
I'm not on the mailing list, so if you need anymore information, email
me directly.
Thank you.
-David van Hoose
davidvh@cox.net
next reply other threads:[~2002-12-07 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 22:02 David van Hoose [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-07 22:03 Kenel compilation failure David van Hoose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DF26FED.5070502@cox.net \
--to=davidvh@cox.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.