All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vadim Abrossimov" <vadim_abrossimov@yahoo.com>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	Jeff Dike <jdike@addtoit.com>
Cc: User-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [PATCH] uml: support a separate build tree; support USER_OBJS dependencies
Date: Mon, 14 Feb 2005 06:28:56 +0100	[thread overview]
Message-ID: <opsl59iieelfdzum@localhost.localdomain> (raw)
In-Reply-To: <20050214011317.GG8859@parcelfarce.linux.theplanet.co.uk>


>
> ACK.  AFAICS, other parts of patch are already covered, except for adding
> arch/um/include/sysdep to search path.  Why do we need that?  Files in
> there get included as <sysdep/blah.h>, not <blah.h>, so...
>
>

I didn't add arch/um/include/sysdep to search path. I agree that it  
useless.
The only difference in include pass betwenn Al's patch and the mine (Dima)  
is the fpllowing:

Al>  ARCH_INCLUDE	:= -I$(ARCH_DIR)/include
Al> +ifneq ($(KBUILD_SRC),)
Al> +ARCH_INCLUDE	+= -I$(ARCH_DIR)/include2
Al> +ARCH_INCLUDE	+= -I$(srctree)/$(ARCH_DIR)/include
Al> +MRPROPER_DIRS	+= $(ARCH_DIR)/include2
Al> +endif

Dima>    include $(MAKEFILES-INCL)
Dima>  endif

Dima> -ARCH_INCLUDE	:= -I$(ARCH_DIR)/include
Dima> +ARCH_INCLUDE	:= -I$(ARCH_DIR)/include \
Dima> +                   $(if $(KBUILD_SRC),  
-I$(objtree)/$(ARCH_DIR)/include2)
Dima> +
Dima>  SYS_DIR		:= $(ARCH_DIR)/include/sysdep-$(SUBARCH)

Actually:
- It's preferable to give an absolute path to include2: it exist only in  
the build tree.
Adding it as a relative path you ask Kbuild to add an absolute path to  
srctree as well.
- we don't need an explicit path to -I$(srctree)/$(ARCH_DIR)/include:  
Kbuild will
do it for us from '-I$(ARCH_DIR)/include'.
You certainly added it because of USER_OBJS. To deal with this issue I  
added
-I$(srctree)/$(ARCH_DIR)/include specifically to USER_CFLAGS:

Dima>  USER_CFLAGS := $(patsubst -I%,,$(CFLAGS))
Dima> -USER_CFLAGS := $(patsubst -D__KERNEL__,,$(USER_CFLAGS))  
$(ARCH_INCLUDE) \
Dima> -	$(MODE_INCLUDE) $(ARCH_USER_CFLAGS)
Dima> +USER_CFLAGS := $(patsubst -D__KERNEL__,,$(USER_CFLAGS))
Dima> +# If building the kernel in a separate tree we need to add this  
path manually.
Dima> +# Note, that for CFLAGS it's done in the generic  
'scripts/Makefile.lib'
Dima> +USER_CFLAGS += $(if $(KBUILD_SRC), -I$(srctree)/$(ARCH_DIR)/include)
Dima> +USER_CFLAGS += $(ARCH_INCLUDE) $(MODE_INCLUDE) $(ARCH_USER_CFLAGS)
Dima> +

Dima


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2005-02-14  5:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-13 14:19 [PATCH] uml: support a separate build tree; support USER_OBJS dependencies Vadim Abrossimov
2005-02-13 18:12 ` Jeff Dike
2005-02-13 16:46   ` Al Viro
2005-02-13 18:58     ` [uml-devel] " Vadim Abrossimov
2005-02-13 21:50       ` Jeff Dike
2005-02-13 23:11         ` Vadim Abrossimov
2005-02-16 18:30           ` Blaisorblade
2005-02-19 10:55             ` Vadim Abrossimov
2005-02-24 16:31               ` Blaisorblade
2005-02-19 14:04             ` Vadim Abrossimov
2005-02-24 18:19               ` Blaisorblade
2005-02-14  1:13         ` Al Viro
2005-02-14  5:28           ` Vadim Abrossimov [this message]
2005-02-13 19:35     ` 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=opsl59iieelfdzum@localhost.localdomain \
    --to=vadim_abrossimov@yahoo.com \
    --cc=User-mode-linux-devel@lists.sourceforge.net \
    --cc=jdike@addtoit.com \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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.