From: Jeff Dike <jdike@addtoit.com>
To: Philippe Roussel <p.o.roussel@free.fr>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] linux-next 20080516 build failure
Date: Fri, 16 May 2008 16:51:03 -0400 [thread overview]
Message-ID: <20080516205103.GA12573@c2.user-mode-linux.org> (raw)
In-Reply-To: <20080516123130.GA11808@coyote.octets.fr>
On Fri, May 16, 2008 at 02:31:30PM +0200, Philippe Roussel wrote:
> Hi
>
> I got this while building randconfigs
>
> CC arch/um/drivers/vde_user.o
> arch/um/drivers/vde_user.c:8:24: error: libvdeplug.h: No such file or directory
> arch/um/drivers/vde_user.c: In function 'vde_user_init':
If you config CONFIG_UML_NET_VDE and don't have the vde stuff
available, something's gotta break. I understand the niceness of
randconfig always working, but this has to fail somehow.
The only way out that I can see is make CONFIG_UML_NET_VDE invisible
to randconfig if vde isn't installed - i.e. if randconfig doesn't
enable stuff that depends on BROKEN, possibly generate a Kconfig which
sniffs the environment and adds that dependency.
OTOH, this makes things magically disappear, whereas the build failure
you encountered makes it immediately obvious what needs to happen in
order to fix the problem.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2008-05-16 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 12:31 [uml-devel] linux-next 20080516 build failure Philippe Roussel
2008-05-16 20:51 ` Jeff Dike [this message]
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=20080516205103.GA12573@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=p.o.roussel@free.fr \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.