From: Michael Cree <mcree@orcon.net.nz>
To: linux-kernel@vger.kernel.org
Cc: linux-alpha@vger.kernel.org
Subject: Alpha: Compilation error 2.6.34-rc1 git a3d3203e4b
Date: Mon, 15 Mar 2010 20:08:08 +1300 [thread overview]
Message-ID: <4B9DDCD8.4070902@orcon.net.nz> (raw)
Compilation error while compiling latest kernel (commit a3d3203e4b) on
Alpha:
CC init/do_mounts.o
In file included from
/home/mjc/linux/linux-git/arch/alpha/include/asm/dma-mapping.h:13,
from include/linux/dma-mapping.h:103,
from
/home/mjc/linux/linux-git/arch/alpha/include/asm/pci.h:7,
from include/linux/pci.h:1209,
from
/home/mjc/linux/linux-git/arch/alpha/include/asm/core_tsunami.h:5,
from
/home/mjc/linux/linux-git/arch/alpha/include/asm/io.h:229,
from include/linux/scatterlist.h:8,
from include/linux/sunrpc/xdr.h:15,
from include/linux/sunrpc/sched.h:17,
from include/linux/sunrpc/auth.h:14,
from include/linux/nfs_fs.h:47,
from init/do_mounts.c:19:
include/asm-generic/dma-mapping-common.h: In function ‘dma_map_sg_attrs’:
include/asm-generic/dma-mapping-common.h:49: error: implicit declaration
of function ‘for_each_sg’
include/asm-generic/dma-mapping-common.h:50: error: expected ‘;’ before
‘kmemcheck_mark_initialized’
make[1]: *** [init/do_mounts.o] Error 1
I note that for_each_sg is defined in include/linux/scatterlist.h, which
arch/alpha/include/asm/dma-mapping.h attempts to load, however
include/linux/scatterlist.h was the one that included (indirectly)
arch/alpha/include/asm/dma-mapping.h. There is therefore a complete
loop of includes from include/linux/scatterlist.h back to itself.
Cheers
Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-alpha" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2010-03-15 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 7:08 Michael Cree [this message]
2010-03-15 7:26 ` Alpha: Compilation error 2.6.34-rc1 git a3d3203e4b Jaswinder Singh Rajput
2010-03-15 10:23 ` FUJITA Tomonori
2010-03-15 21:50 ` Matt Turner
2010-03-15 22:54 ` Will L Givens
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=4B9DDCD8.4070902@orcon.net.nz \
--to=mcree@orcon.net.nz \
--cc=linux-alpha@vger.kernel.org \
--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 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).