From: Erik Paulson <epaulson@cs.wisc.edu>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] building 2.6.24-rc1 with VDE in a non-standard location?
Date: Thu, 1 Nov 2007 21:27:49 -0500 [thread overview]
Message-ID: <20071102022749.GB8583@swingline.cs.wisc.edu> (raw)
I'm trying to build UML with VDE support turned on. However, I don't
have root on my host machine, so when I installed VDE I put it in a
non-standard location.
How do you pass extra -L and -I flags to the kernel build process? I
tried adding
make linux ARCH=um CFLAGS=-I/path/to/my/vde/include
with no go, and I tried adding the include path to
HOSTCFLAGS in the top level Makefile rules, but that also didn't
work.
I got it to build by just sticking the right -I and -L flags in
arch/um/drivers/Makefile
Is there another, more standard Linux kernel way that's equivalent to
./configure --with-package=/path/
Thanks,
-Erik
-------------------------------------------------------------------------
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 reply other threads:[~2007-11-02 2:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 2:27 Erik Paulson [this message]
2007-11-02 15:51 ` [uml-devel] building 2.6.24-rc1 with VDE in a non-standard location? 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
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=20071102022749.GB8583@swingline.cs.wisc.edu \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox