From: Eric Sandeen <sandeen@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: hch@infradead.org, sam@ravnborg.org,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: xfs: Makefile-linux-2.6 => Makefile?
Date: Tue, 10 Jan 2006 09:14:05 -0600 [thread overview]
Message-ID: <43C3CF3D.4000701@sgi.com> (raw)
In-Reply-To: <20060109234532.78bda36a.akpm@osdl.org>
Andrew Morton wrote:
> It'd be nice to fix this:
>
> bix:/usr/src/25> make fs/xfs/linux-2.6/xfs_iops.o
> SPLIT include/linux/autoconf.h -> include/config/*
> SHIPPED scripts/genksyms/lex.c
> SHIPPED scripts/genksyms/parse.h
> SHIPPED scripts/genksyms/keywords.c
> HOSTCC scripts/genksyms/lex.o
> SHIPPED scripts/genksyms/parse.c
> HOSTCC scripts/genksyms/parse.o
> HOSTLD scripts/genksyms/genksyms
> HOSTCC scripts/mod/file2alias.o
> HOSTCC scripts/mod/modpost.o
> HOSTLD scripts/mod/modpost
> scripts/Makefile.build:15: /usr/src/devel/fs/xfs/linux-2.6/Makefile: No such file or directory
> make[1]: *** No rule to make target `/usr/src/devel/fs/xfs/linux-2.6/Makefile'. Stop.
> make: *** [fs/xfs/linux-2.6/xfs_iops.o] Error 2
I'll see what I can do to fix this up and a couple of other kbuild issues I've
run into recently.
Thanks,
-Eric
next prev parent reply other threads:[~2006-01-10 15:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 16:42 xfs: Makefile-linux-2.6 => Makefile? Sam Ravnborg
2006-01-09 16:46 ` Christoph Hellwig
2006-01-09 17:19 ` Sam Ravnborg
2006-01-09 21:01 ` Sam Ravnborg
2006-01-09 21:05 ` Christoph Hellwig
2006-01-09 21:18 ` Sam Ravnborg
2006-01-09 21:03 ` Eric Sandeen
2006-01-09 21:20 ` Sam Ravnborg
2006-01-09 21:23 ` Eric Sandeen
2006-01-09 21:45 ` Sam Ravnborg
2006-01-10 7:45 ` Andrew Morton
2006-01-10 15:14 ` Eric Sandeen [this message]
2006-01-10 16:34 ` Eric Sandeen
2006-01-10 20:02 ` Sam Ravnborg
2006-01-16 23:19 ` Sam Ravnborg
2006-01-17 3:40 ` Eric Sandeen
2006-01-10 20:00 ` Sam Ravnborg
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=43C3CF3D.4000701@sgi.com \
--to=sandeen@sgi.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=sam@ravnborg.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.