linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Peter Teoh <htmldeveloper@gmail.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] arch/um/Makefile:100: *** missing separator. Stop.
Date: Fri, 2 May 2008 15:52:30 -0400	[thread overview]
Message-ID: <20080502195230.GA10369@c2.user-mode-linux.org> (raw)
In-Reply-To: <804dabb00805021049q773ddee8i1f2a21a05368b74e@mail.gmail.com>

On Sat, May 03, 2008 at 01:49:40AM +0800, Peter Teoh wrote:
> This is what I have done, not sure if anything wrong:
> 
> a.   mkdir obj;make oldconfig ARCH=um O=obj
> 
> This created one file in obj, but after that created infinite number
> of make -C processes running in the background.....I stopped that.
> 
> ps -ef and the following repeated MANY MANY TIMES:
> 
> root     32742 32658  0 01:13 pts/2    00:00:00 make -C
> /mnt/hd0/download/linux-2.6-latest KBUILD_SRC= oldconfig
> root     32745 32742  0 01:13 pts/2    00:00:00 make -C
> /mnt/hd0/download/linux-2.6-latest/obj
> /mnt/hd0/download/linux-2.6-latest/obj KBUILD_SRC=/mnt/hd0/dow

The only thing that makes any sense to me is that you have a severely
broken make.

> So, not okay.
> 
> b.   mkdir obj; make ARCH=um O=obj
> 
> As per instructed.....it works except it complained no config file (in
> obj directory), and suggested to do a mrproper for the current parent
> directory.   So I copied the .config to obj directory, make mrproper
> in parent directory, and then cd to obj and make oldconfig there, and
> then "make":
> 
> cp .config obj
> make mrproper
> cd obj

Why did you do this?  You're never supposed to cd to the object
directory and run make in it.

Also, you should have ARCH=um on all make commands, including
mrproper.

				Jeff

-- 
Work email - jdike at linux dot intel dot com

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
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:[~2008-05-02 19:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 15:53 [uml-devel] arch/um/Makefile:100: *** missing separator. Stop Peter Teoh
2008-04-28 18:55 ` Jeff Dike
2008-04-29 12:02   ` Peter Teoh
2008-04-29 15:37     ` Jeff Dike
2008-04-29 16:15       ` Peter Teoh
2008-04-29 17:29         ` Jeff Dike
2008-04-30 15:04           ` Peter Teoh
2008-04-30 15:14             ` Antoine Martin
2008-04-30 16:24       ` Peter Teoh
2008-04-30 18:47         ` Jeff Dike
2008-04-30 23:35           ` Peter Teoh
2008-05-01 15:15             ` Jeff Dike
2008-05-01 16:13               ` Peter Teoh
2008-05-01 16:18                 ` Peter Teoh
2008-05-02 15:50                   ` Jeff Dike
2008-05-02 17:49                     ` Peter Teoh
2008-05-02 19:52                       ` Jeff Dike [this message]
2008-05-03  6:18                         ` Peter Teoh

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=20080502195230.GA10369@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=htmldeveloper@gmail.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