From: Sam Ravnborg <sam@ravnborg•org>
To: David Miller <davem@davemloft•net>
Cc: sfr@canb•auug.org.au, linux-next@vger•kernel.org,
geert@linux-m68k•org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: m68k build failure
Date: Wed, 30 Jul 2008 10:49:35 +0200 [thread overview]
Message-ID: <20080730084935.GA18545@uranus.ravnborg.org> (raw)
In-Reply-To: <20080730.010234.193703201.davem@davemloft.net>
On Wed, Jul 30, 2008 at 01:02:34AM -0700, David Miller wrote:
> From: Stephen Rothwell <sfr@canb•auug.org.au>
> Date: Wed, 30 Jul 2008 17:52:33 +1000
>
> > linux-next (version next-20080729) build (m68k defconfig) failed like this;
> >
> > In file included from arch/m68k/sun3/idprom.c:16:
> > include2/asm/idprom.h:3:30: error: asm-sparc/idprom.h: No such file or directory
>
> Yes, Sam told the m68k folks this would happen and that they
> would need to resolve it somehow.
>
> Perhaps as a quick fix we can just copy sparc's idprom.h into
> asm-m68k/idprom.h
Full list of relevant files:
include/asm-m68k/contregs.h:#include <asm-sparc/contregs.h>
include/asm-m68k/fbio.h:#include <asm-sparc/fbio.h>
include/asm-m68k/idprom.h:#include <asm-sparc/idprom.h>
I will try to take a look at it tonight. m68knommu is
also part of the game.
Need to get x86 + um working with arch/x86/include first though.
Sam
next prev parent reply other threads:[~2008-07-30 8:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 7:52 linux-next: m68k build failure Stephen Rothwell
2008-07-30 7:54 ` Stephen Rothwell
2008-07-30 8:02 ` David Miller
2008-07-30 8:49 ` Sam Ravnborg [this message]
2008-08-01 5:37 ` Stephen Rothwell
2008-08-01 13:52 ` Geert Uytterhoeven
2008-08-01 20:41 ` Sam Ravnborg
2008-08-02 4:06 ` Stephen Rothwell
2008-08-03 20:00 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2008-08-28 6:50 Stephen Rothwell
2008-08-28 6:59 ` Ingo Molnar
2008-12-09 6:45 Stephen Rothwell
2008-12-09 8:00 ` David Miller
2008-12-09 8:50 ` Stephen Rothwell
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=20080730084935.GA18545@uranus.ravnborg.org \
--to=sam@ravnborg$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=geert@linux-m68k$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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