All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: cscope build warning [Was: mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded]
Date: Tue, 13 Nov 2007 14:27:12 +0100	[thread overview]
Message-ID: <20071113132712.GA31270@uranus.ravnborg.org> (raw)
In-Reply-To: <47399B4D.5040208@gmail.com>

On Tue, Nov 13, 2007 at 01:40:45PM +0100, Jiri Slaby wrote:
> On 11/13/2007 01:15 PM, akpm@linux-foundation.org wrote:
> > The mm snapshot broken-out-2007-11-13-04-14.tar.gz has been uploaded to
> 
> $ uname -a
> Linux bellona 2.6.23-rc8-mm2_64 #58 SMP Fri Sep 28 08:52:12 CEST 2007 x86_64
> x86_64 x86_64 GNU/Linux
> $ make O=../bu cscope
>   FILELST cscope.files
> find: /home/l/latest/xxx/arch/x86_64: není souborem ani adresářem
>   MAKE    cscope.out
> 

I have following fix queued in my inbox:

This patch fixed the following errors when doing "make cscope" and
"make cscope ARCH=um".

  FILELST cscope.files
find: arch/i386: No such file or directory
  MAKE    cscope.out


  FILELST cscope.files
find: include/asm-i386: No such file or directory
  MAKE    cscope.out


Signed-off-by: WANG Cong <xiyou.wangcong@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>

---

diff --git a/Makefile b/Makefile
index e28dde8..01335ca 100644
--- a/Makefile
+++ b/Makefile
@@ -1322,6 +1322,7 @@ ALLINCLUDE_ARCHS := $(ARCH) $(SUBARCH)
 else
 ALLINCLUDE_ARCHS := $(SRCARCH)
 endif
+ALLINCLUDE_ARCHS := $(shell echo $(ALLINCLUDE_ARCHS)|sed -e "s/i386/x86/" -e "s/x86_64/x86/")
 else
 #Allow user to specify only ALLSOURCE_PATHS on the command line, keeping existing behavour.
 ALLINCLUDE_ARCHS := $(ALLSOURCE_ARCHS)
@@ -1331,7 +1332,7 @@ endif
 ifeq ($(ARCH), $(SRCARCH))
 ALLSOURCE_ARCHS := $(ARCH)
 else
-ALLSOURCE_ARCHS := $(ARCH) $(SRCARCH)
+ALLSOURCE_ARCHS := $(shell echo $(ARCH) $(SRCARCH)|sed -e "s/i386/x86/" -e "s/x86_64/x86/")
 endif
 
 define find-sources


  reply	other threads:[~2007-11-13 13:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 12:15 mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded akpm
2007-11-13 12:40 ` cscope build warning [Was: mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded] Jiri Slaby
2007-11-13 13:27   ` Sam Ravnborg [this message]
2007-11-13 13:36     ` Jiri Slaby
2007-11-13 12:50 ` nfs functions undefined " Jiri Slaby
2007-11-13 17:34   ` [PATCH] " Randy Dunlap
2007-11-13 19:43     ` Andrew Morton
2007-11-13 14:43 ` mm snapshot broken-out-2007-11-13-04-14 Build Fails at memory.c Kamalesh Babulal
2007-11-13 15:17   ` Martin Schwidefsky
2007-11-13 15:30     ` Kamalesh Babulal
2007-11-13 15:29   ` Martin Schwidefsky
2007-11-13 15:11 ` mm snapshot broken-out-2007-11-13-04-14 Build Fails due kobject cleanup Kamalesh Babulal
2007-11-13 15:22 ` mm snapshot broken-out-2007-11-13-04-14 Build Fails due kobject cleanup (Resend) Kamalesh Babulal
2007-11-13 19:51 ` mm snapshot broken-out-2007-11-13-04-14 Build Fails - linking when !CONFIG_NFS_V4 Kamalesh Babulal
2007-11-14  5:23   ` Randy Dunlap
2007-11-14  0:20 ` mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded Kevin Winchester
2007-11-14  1:11   ` Andrew Morton
2007-11-14  1:15     ` Randy Dunlap

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=20071113132712.GA31270@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.