linux-kernel - Re: linux-next: m68k build failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 2 Aug 2008 14:06:50 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	David Miller <davem@...emloft.net>, linux-next@...r.kernel.org,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	Linux/m68k <linux-m68k@...r.kernel.org>
Subject: Re: linux-next: m68k build failure

Hi Sam,

On Fri, 1 Aug 2008 22:41:57 +0200 Sam Ravnborg <sam@...nborg.org> wrote:
>
> On Fri, Aug 01, 2008 at 03:52:22PM +0200, Geert Uytterhoeven wrote:
> > 
> > BTW, is there a (good) way to have this without duplicating those header files?
> 
> The only solution I can come up with right now is:
> 
> Makefile:
> ccflags-y += -Iarch/sparc/include
> 
> foo.c:
> #include <asm/fbio.h>
> 
> Disadvantage is that we loose the explicit documentation that this
> is header files from another architecture.
> So we should at least add a comment saying this.
> 
> And the above would not work if the file has same filename,
> but then that is not a likely situation either.

There is at least one of the m68k header files that includes the sparc
file of the same name and then does other stuff.  So this scheme would
not cover that  (unless we used #include_next?) 

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped