mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17 du jour on SPARC64: Build failure
Date: Mon, 26 Jun 2006 18:22:05 -0700	[thread overview]
Message-ID: <20060626182205.ba9392d2.rdunlap@xenotime.net> (raw)
In-Reply-To: <200606270041.k5R0fZqd008665@laptop11.inf.utfsm.cl>

On Mon, 26 Jun 2006 20:41:35 -0400 Horst von Brand wrote:

>   CC      arch/sparc64/kernel/devices.o
> In file included from include/linux/dma-mapping.h:27,
>                  from include/asm/sbus.h:10,
>                  from include/asm/dma.h:14,
>                  from include/linux/bootmem.h:8,
>                  from arch/sparc64/kernel/devices.c:15:
> include/asm/dma-mapping.h: In function `dma_sync_single_range_for_cpu':
> include/asm/dma-mapping.h:186: warning: implicit declaration of function `dma_sy
> nc_single_for_cpu'
> include/asm/dma-mapping.h: In function `dma_sync_single_range_for_device':
> include/asm/dma-mapping.h:195: warning: implicit declaration of function `dma_sy
> nc_single_for_device'
> make[1]: *** [arch/sparc64/kernel/devices.o] Error 1
> make: *** [arch/sparc64/kernel] Error 2
> 
> Configuration is attached.

CONFIG_PCI is not set.  That's the build problem, although
I don't see which file #includes it.
The bad news is that when CONFIG_PCI=n, those functions just do
	BUG();
anyway, so it won't help you much.

~Randy

  parent reply	other threads:[~2006-06-27  1:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27  0:41 Horst von Brand
2006-06-27  1:12 ` David Miller
2006-06-27  1:22 ` Randy.Dunlap [this message]
2006-06-27  9:12   ` David Miller
2006-06-27 16:02     ` Randy.Dunlap

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=20060626182205.ba9392d2.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vonbrand@inf.utfsm.cl \
    /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

all inboxes | Powered by JetHome®