From: Jeff Dike <jdike@addtoit.com>
To: Erik Paulson <epaulson@cs.wisc.edu>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] building 2.6.24-rc1 with VDE in a non-standard location?
Date: Mon, 12 Nov 2007 11:29:15 -0500 [thread overview]
Message-ID: <20071112162915.GA6862@c2.user-mode-linux.org> (raw)
In-Reply-To: <20071111194711.GA16100@swingline.cs.wisc.edu>
On Sun, Nov 11, 2007 at 01:47:16PM -0600, Erik Paulson wrote:
> Good news - this doesn't happen with 2.6.24-rc2. defconfig builds with
> a CFLAGS on the commandline
We seem to have cleared up the x86/kbuild breakage for now.
> Unfortunately, VDE still doesn't compile - the CFLAGS aren't being passed
> along to arch/um/drivers:
Yeah, it's not obvious why - I need to look into this.
> make linux ARCH=um CFLAGS=-I/scratch/epaulson/vde/include LDFLAGS=-L/scratch/epaulson/vde/lib V=1
BTW, I misspelled LDFLAGS - you'll have to use LFLAGS until I fix this.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2007-11-12 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 2:27 [uml-devel] building 2.6.24-rc1 with VDE in a non-standard location? Erik Paulson
2007-11-02 15:51 ` Jeff Dike
2007-11-02 16:22 ` Erik Paulson
2007-11-02 17:25 ` Jeff Dike
2007-11-05 17:12 ` Jeff Dike
2007-11-05 17:57 ` Erik Paulson
2007-11-11 19:47 ` Erik Paulson
2007-11-12 16:29 ` Jeff Dike [this message]
2007-11-18 16:11 ` 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=20071112162915.GA6862@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=epaulson@cs.wisc.edu \
--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.