linux-kernel - Re: linux-next: Tree for March 13

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] [day] [month] [year] [list]

Date:	Fri, 14 Mar 2008 13:44:04 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Linux/m68k <linux-m68k@...ts.linux-m68k.org>
Subject: Re: linux-next: Tree for March 13

Hi Geert,

On Thu, 13 Mar 2008 11:31:39 +0100 (CET) Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
> I noticed you added `m68k-allnoconfig', which fails because of the following

This was an experiment.  I disabled it again.

> reasons:
>   - There's no single CPU type enabled, hence we get:
> 
> 	#define FPSTATESIZE error no_cpu_type_configured
> 
>   - There's no single platform type enabled, hence we get no definition of
>     NR_IRQS:
> 
> 	#error unknown nr of irqs
> 
> Well yes, these are all `features' of allnoconfig :-)
> Or should we make sure you cannot build invalid configs like this?

I think that for architectures that do allow allnoconfig to build, they
have a fallback for these situations.  allnoconfig is a good quick way to
see if the core code builds ok for an architecture.

So maybe you could choose (even at random) defaults for the above two
things rather than erroring.  That would also help with randconfig builds.

If you make it work, let me know and I will reenable the build.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped