linux-um archives
 help / color / mirror / Atom feed
From: Erik Paulson <epaulson@cs.wisc.edu>
To: Jeff Dike <jdike@addtoit.com>
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: Sun, 11 Nov 2007 13:47:16 -0600	[thread overview]
Message-ID: <20071111194711.GA16100@swingline.cs.wisc.edu> (raw)
In-Reply-To: <20071105171213.GA7296@c2.user-mode-linux.org>

On Mon, Nov 05, 2007 at 12:12:13PM -0500, Jeff Dike wrote:
> On Fri, Nov 02, 2007 at 11:22:44AM -0500, Erik Paulson wrote:
> > running:
> > make linux ARCH=um CFLAGS=-I/scratch/epaulson/vde/include
> 
> This isn't going to help with the compilation problems, but the patch
> below seems to pass LFLAGS from the command line through to ld nicely.
> 
> >   CC      arch/um/kernel/skas/mmu.o
> > In file included from include/asm/processor-generic.h:13,
> >                  from include/asm/processor.h:77,
> >                  from include/asm/thread_info.h:11,
> >                  from include/linux/thread_info.h:21,
> >                  from include/linux/preempt.h:9,
> >                  from include/linux/spinlock.h:49,
> >                  from include/linux/mmzone.h:7,
> >                  from include/linux/gfp.h:4,
> >                  from include/linux/mm.h:8,
> >                  from arch/um/kernel/skas/mmu.c:6:
> > include/asm/ptrace.h:50: warning: "struct user_fxsr_struct" declared inside parameter list
> > include/asm/ptrace.h:50: warning: its scope is only this definition or declaration, which is probably not what you want
> > include/asm/ptrace.h:52: warning: "struct user_fxsr_struct" declared
> > inside parameter list
> 
> Does this happen with plain old defconfig?
> 
> 				Jeff

Good news - this doesn't happen with 2.6.24-rc2. defconfig builds with
a CFLAGS on the commandline

Unfortunately, VDE still doesn't compile - the CFLAGS aren't being passed 
along to arch/um/drivers:

make linux ARCH=um CFLAGS=-I/scratch/epaulson/vde/include LDFLAGS=-L/scratch/epaulson/vde/lib V=1

<...>
make -f scripts/Makefile.build obj=arch/um/drivers
  gcc -Wp,-MD,arch/um/drivers/.vde_user.o.d  -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Os -D__arch_um__ -DSUBARCH=\"i386\" -Dvmap=kernel_vmap -Din6addr_loopback=kernel_in6addr_loopback -Din6addr_any=kernel_in6addr_any -DCONFIG_X86_32 -march=i686 -mpreferred-stack-boundary=2 -ffreestanding -D_LARGEFILE64_SOURCE  -fno-unit-at-a-time -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -Wdeclaration-after-statement -Iarch/um/include -I/scratch/epaulson/uml/linux-2.6.24-rc2/linux-2.6.23/arch/um/include/skas -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_LARGEFILE64_SOURCE  -c -o arch/um/drivers/vde_user.o arch/um/drivers/vde_user.c
arch/um/drivers/vde_user.c:8:24: libvdeplug.h: No such file or directory



-------------------------------------------------------------------------
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

  parent reply	other threads:[~2007-11-11 20:19 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 [this message]
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=20071111194711.GA16100@swingline.cs.wisc.edu \
    --to=epaulson@cs.wisc.edu \
    --cc=jdike@addtoit.com \
    --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