From: Wes Kurdziolek <wkurdzio@cs.vt.edu>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: Compile problem w/ 2.4.20-pre7-ac2
Date: 19 Sep 2002 00:22:21 -0400 [thread overview]
Message-ID: <1032409341.6480.2.camel@yavin> (raw)
Found a compile problem w/ 2.4.20-pre7-ac2 when attempting to compile
the PIIX driver:
make[4]: Entering directory
`/usr/src/linux-2.4.20-pre7-ac2/drivers/ide/pci'
gcc -D__KERNEL__ -I/usr/src/linux-2.4.20-pre7-ac2/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
-I../ -nostdinc -iwithprefix include -DKBUILD_BASENAME=piix -c -o
piix.o piix.c
piix.c: In function `init_chipset_piix':
piix.c:533: init_chipset_piix causes a section type conflict
piix.c: In function `piix_init_one':
piix.c:677: piix_init_one causes a section type conflict
piix.c: At top level:
piix.c:696: warning: `piix_remove_one' defined but not used
make[4]: *** [piix.o] Error 1
make[4]: Leaving directory
`/usr/src/linux-2.4.20-pre7-ac2/drivers/ide/pci'
make[3]: *** [first_rule] Error 2
make[3]: Leaving directory
`/usr/src/linux-2.4.20-pre7-ac2/drivers/ide/pci'
make[2]: *** [_subdir_pci] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.20-pre7-ac2/drivers/ide'
make[1]: *** [_subdir_ide] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.20-pre7-ac2/drivers'
make: *** [_dir_drivers] Error 2
yavin:/usr/src/linux-2.4.20-pre7-ac2# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 20011002 (Debian prerelease)
yavin:/usr/src/linux-2.4.20-pre7-ac2# ld -v
GNU ld version 2.13.90.0.4 20020814 Debian GNU/Linux
yavin:/usr/src/linux-2.4.20-pre7-ac2#
next reply other threads:[~2002-09-19 4:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 4:22 Wes Kurdziolek [this message]
2002-09-19 8:05 ` Compile problem w/ 2.4.20-pre7-ac2 Jens Axboe
2002-09-19 10:30 ` Alan Cox
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=1032409341.6480.2.camel@yavin \
--to=wkurdzio@cs.vt.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--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.