public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: devzero@web.de
Cc: linux-kernel@vger.kernel.org, 12o3l@tiscali.nl
Subject: Re: build failure, missing libvdeplug.h?
Date: Fri, 2 Nov 2007 11:42:54 -0400	[thread overview]
Message-ID: <20071102154254.GA5760@c2.user-mode-linux.org> (raw)
In-Reply-To: <2061698400@web.de>

On Fri, Nov 02, 2007 at 01:05:59PM +0100, devzero@web.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

  reply	other threads:[~2007-11-02 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 12:05 build failure, missing libvdeplug.h? devzero
2007-11-02 15:42 ` Jeff Dike [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-29 15:24 Roel Kluin
2007-10-29 15:41 ` Roel Kluin
2007-10-29 15:57   ` Gabriel C
2007-10-29 16:03 ` Jeff Dike

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=20071102154254.GA5760@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=12o3l@tiscali.nl \
    --cc=devzero@web.de \
    --cc=linux-kernel@vger.kernel.org \
    /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