From: Martin Costabel <costabel@wanadoo.fr>
To: linuxppc-user@lists.linuxppc.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Kernel Compile Fun
Date: Tue, 04 Jan 2000 10:30:04 +0100 [thread overview]
Message-ID: <3871BD9C.2DB00160@wanadoo.fr> (raw)
In-Reply-To: Pine.GSO.4.10.10001031922430.26986-100000@unix1.wm.edu
This has been discussed for at least 8 months (see the list archives),
and it was always asked why this is not corrected in the kernel trees. I
ask this again.
Some explanation: In arch/ppc/kernel/pmac_setup.c, the header file
<asm/dma.h> is included via <asm/scatterlist.h> via
"drivers/scsi/scsi.h", but only
#if defined(CONFIG_SCSI) && defined(CONFIG_BLK_DEV_SD)
On the other hand, the variables ISA_DMA_THRESHOLD and so on are used
outside of any #if. This certainly looks like a bug.
--
Martin
Rob Lineweaver wrote:
>
> This is from the list archives:
>
> You can fix this by inserting the line
>
> #include <asm/dma.h>
> into the file pmac_setup.c.
>
> Thanks to Michael Fenske, who originally posted that message. That fixed
> the problem for me.
>
> hope that works
>
> Rob Lineweaver
> :)
>
> On Mon, 3 Jan 2000, Kyle R. Green wrote:
>
> >
> > I am having the worst possible time getting a newer kernel to compile. I
> > received this error with both the stock 2.2.13 (and 2.2.14-pre18) kernel
> > on ftp.kernel.org and the linux-pmac-stable tree I rsynced from
> > linuxcare.com.au today:
> >
> > make[1]: Entering directory `/usr/src/linux-pmac-stable/arch/ppc/kernel'
> > gcc -D__KERNEL__ -I/usr/src/linux-pmac-stable/include -Wall
> > -Wstrict-prototypes
> > -O2 -fomit-frame-pointer -fno-strict-aliasing -D__powerpc__ -fsigned-char
> > -msoft
> > -float -pipe -fno-builtin -ffixed-r2 -Wno-uninitialized -mmultiple
> > -mstring -c
> > -o pmac_setup.o pmac_setup.c
> > pmac_setup.c: In function `pmac_init':
> > pmac_setup.c:597: `ISA_DMA_THRESHOLD' undeclared (first use in this
> > function)
> > pmac_setup.c:597: (Each undeclared identifier is reported only once
> > pmac_setup.c:597: for each function it appears in.)
> > pmac_setup.c:598: `DMA_MODE_READ' undeclared (first use in this function)
> > pmac_setup.c:599: `DMA_MODE_WRITE' undeclared (first use in this function)
> > make[1]: *** [pmac_setup.o] Error 1
> > make[1]: Leaving directory `/usr/src/linux-pmac-stable/arch/ppc/kernel'
> > make: *** [_dir_arch/ppc/kernel] Error 2
> > [root@portamoose linux-pmac-stable]#
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
parent reply other threads:[~2000-01-04 9:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.GSO.4.10.10001031922430.26986-100000@unix1.wm.edu>]
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=3871BD9C.2DB00160@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).