From: Alex Romosan <romosan@sycorax.lbl.gov>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-rc5
Date: Tue, 27 May 2003 13:53:48 -0700 [thread overview]
Message-ID: <8765nw2js3.fsf@sycorax.lbl.gov> (raw)
In-Reply-To: <Pine.LNX.4.55L.0305271640320.9487@freak.distro.conectiva> (message from Marcelo Tosatti on Tue, 27 May 2003 16:41:16 -0300 (BRT))
Marcelo Tosatti <marcelo@conectiva.com.br> writes:
> Mainly due to a IDE DMA problem which would happen on boxes with lots of
> RAM, here is -rc5.
>
> As I always ask, please test.
i get the following error:
make[5]: Entering directory `/usr/src/linux/drivers/ide/pci'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=athlon -I../ -nostdinc -iwithprefix include -DKBUILD_BASENAME=via82cxxx -c -o via82cxxx.o via82cxxx.c
via82cxxx.c:77: error: `PCI_DEVICE_ID_VIA_8237' undeclared here (not in a function)
via82cxxx.c:77: error: initializer element is not constant
via82cxxx.c:77: error: (near initialization for `via_isa_bridges[0].id')
via82cxxx.c:77: error: initializer element is not constant
via82cxxx.c:77: error: (near initialization for `via_isa_bridges[0]')
via82cxxx.c:78: error: initializer element is not constant
via82cxxx.c:78: error: (near initialization for `via_isa_bridges[1]')
via82cxxx.c:79: error: initializer element is not constant
via82cxxx.c:79: error: (near initialization for `via_isa_bridges[2]')
via82cxxx.c:80: error: initializer element is not constant
via82cxxx.c:80: error: (near initialization for `via_isa_bridges[3]')
via82cxxx.c:81: error: initializer element is not constant
via82cxxx.c:81: error: (near initialization for `via_isa_bridges[4]')
via82cxxx.c:82: error: initializer element is not constant
via82cxxx.c:82: error: (near initialization for `via_isa_bridges[5]')
via82cxxx.c:83: error: initializer element is not constant
via82cxxx.c:83: error: (near initialization for `via_isa_bridges[6]')
via82cxxx.c:84: error: initializer element is not constant
via82cxxx.c:84: error: (near initialization for `via_isa_bridges[7]')
via82cxxx.c:85: error: initializer element is not constant
via82cxxx.c:85: error: (near initialization for `via_isa_bridges[8]')
via82cxxx.c:86: error: initializer element is not constant
via82cxxx.c:86: error: (near initialization for `via_isa_bridges[9]')
via82cxxx.c:87: error: initializer element is not constant
via82cxxx.c:87: error: (near initialization for `via_isa_bridges[10]')
via82cxxx.c:88: error: initializer element is not constant
via82cxxx.c:88: error: (near initialization for `via_isa_bridges[11]')
via82cxxx.c:89: error: initializer element is not constant
via82cxxx.c:89: error: (near initialization for `via_isa_bridges[12]')
via82cxxx.c:90: error: initializer element is not constant
via82cxxx.c:90: error: (near initialization for `via_isa_bridges[13]')
via82cxxx.c:91: error: initializer element is not constant
via82cxxx.c:91: error: (near initialization for `via_isa_bridges[14]')
via82cxxx.c:92: error: initializer element is not constant
via82cxxx.c:92: error: (near initialization for `via_isa_bridges[15]')
via82cxxx.c:93: error: initializer element is not constant
via82cxxx.c:93: error: (near initialization for `via_isa_bridges[16]')
via82cxxx.c:94: error: initializer element is not constant
via82cxxx.c:94: error: (near initialization for `via_isa_bridges[17]')
via82cxxx.c:95: error: initializer element is not constant
via82cxxx.c:95: error: (near initialization for `via_isa_bridges[18]')
make[5]: *** [via82cxxx.o] Error 1
make[5]: Leaving directory `/usr/src/linux/drivers/ide/pci'
make[4]: *** [first_rule] Error 2
make[4]: Leaving directory `/usr/src/linux/drivers/ide/pci'
make[3]: *** [_subdir_pci] Error 2
make[3]: Leaving directory `/usr/src/linux/drivers/ide'
make[2]: *** [_subdir_ide] Error 2
make[2]: Leaving directory `/usr/src/linux/drivers'
make[1]: *** [_dir_drivers] Error 2
make[1]: Leaving directory `/usr/src/linux'
make: *** [stamp-build] Error 2
this compiled in -rc4.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
next prev parent reply other threads:[~2003-05-27 20:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 19:41 Linux 2.4.21-rc5 Marcelo Tosatti
2003-05-27 20:53 ` Alex Romosan [this message]
2003-05-27 20:36 ` Alan Cox
2003-05-27 21:53 ` Marcelo Tosatti
2003-05-27 22:35 ` [PATCH] IDE config correctness (was: Linux 2.4.21-rc5) Carl-Daniel Hailfinger
2003-05-28 5:46 ` Linux 2.4.21-rc5: [RESENT PATCH] kernel with Old ide hard disk only support doesn't build Jerome Chantelauze
2003-05-28 8:10 ` Linux 2.4.21-rc5 Olaf Dietrich
-- strict thread matches above, loose matches on Subject: below --
2003-05-27 20:48 Mitch
2003-05-27 21:17 ` Marc-Christian Petersen
2003-05-27 21:45 ` Adrian Bunk
2003-05-27 20:56 Margit Schubert-While
2003-05-27 21:33 Chris Rankin
2003-05-28 2:25 Jason Papadopoulos
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=8765nw2js3.fsf@sycorax.lbl.gov \
--to=romosan@sycorax.lbl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox