linux-kernel - Re: build failure, missing libvdeplug.h?

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, 2 Nov 2007 11:42:54 -0400
From:	Jeff Dike <jdike@...toit.com>
To:	devzero@....de
Cc:	linux-kernel@...r.kernel.org, 12o3l@...cali.nl
Subject: Re: build failure, missing libvdeplug.h?

On Fri, Nov 02, 2007 at 01:05:59PM +0100, devzero@....de wrote:
> I tried 2.6.24-rc1-git11 with "allmodconfig ARCH=um" today.
> 
> this gave at least two errors - i needed to set CONFIG_SMP=n 

SMP should depend on BROKEN for now, and I thought it did.

> and CONFIG_UML_NET_VDE=n to make it compile.

For this, my immediate reaction is that if you're going to build
something, the dependencies should be there.  However, I guess we
should have some sympathy for the automatic allyesconfig builders.
I'm wondering whether, instead of failing the build if headers or
libraries aren't available, compile in some sort of stub which will
produce a run-time error instead.

The violates my preference to have error detected as early as
possible, but maybe it's preferable to the current situation.

				Jeff

-- 
Work email - jdike at linux dot intel dot com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/