From: Sam Ravnborg <sam@ravnborg.org>
To: Kai Germaschewski <kai-germaschewski@uiowa.edu>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: RfC: Don't cd into subdirs during kbuild
Date: Thu, 3 Oct 2002 21:26:18 +0200 [thread overview]
Message-ID: <20021003212618.A17403@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0210022153090.10307-100000@chaos.physics.uiowa.edu>; from kai-germaschewski@uiowa.edu on Wed, Oct 02, 2002 at 09:59:00PM -0500
On Wed, Oct 02, 2002 at 09:59:00PM -0500, Kai Germaschewski wrote:
>
> Hi,
>
> I'd appreciate to get comments on the appended patch. It's mostly cleanups
> and the like, but the interesting part is the last cset, which is actually
> fairly small:
Tried out what I pulled from linux-2.5.make
1) warning present in Makefile
2) Annoying /././ when doing make dep
3) Did a ld built-in.o in scripts, despite obj-y is empty
- When i changed "=" to ":=" to fix next error ar failed.
ifdef O_TARGET replaced with ifdef obj-y to make it work
4) Could not link, no *.o file were used as parameters to ld
cmd_link_o_target := $(if $(strip $(obj-y)),\
$(LD) $(LDFLAGS) $(EXTRA_LDFLAGS) -r -o $@ $(filter $(obj-y), $^),\
rm -f $@; $(AR) rcs $@)
$(O_TARGET): $(obj-y) FORCE
@echo XXXXX $^
@echo $(obj-y) - $@
Result:
make[1]: Entering directory `/home/sam/src/linux/kernel/bk/kai-make/init'
Generating /home/sam/src/linux/kernel/bk/kai-make/include/linux/compile.h (unchanged)
XXXXX main.o version.o do_mounts.o FORCE
./main.o ./version.o ./do_mounts.o - built-in.o
ld -m elf_i386 -r -o
ld: unrecognized option '-o'
ld: use the --help option for usage information
It seems that make strips "./" in front of all .o files listed in obj-y
Utilising $(filter-out FORCE,$(obj-y) did the trick for me.
[sam@mars kai-make]$ make -v
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Hmmm, was the stuff present at bkbits incomplete?
Sam
next prev parent reply other threads:[~2002-10-03 19:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 2:59 Kai Germaschewski
2002-10-03 3:32 ` Andreas Dilger
2002-10-03 5:18 ` [kbuild-devel] " Peter Samuelson
2002-10-03 14:54 ` Kai Germaschewski
2002-10-03 8:21 ` Xavier Bestel
2002-10-03 14:56 ` Kai Germaschewski
2002-10-03 15:31 ` Xavier Bestel
2002-10-03 20:41 ` Peter Samuelson
2002-10-03 14:05 ` John Levon
2002-10-03 14:27 ` Kai Germaschewski
2002-10-03 14:45 ` John Levon
2002-10-03 19:26 ` Sam Ravnborg [this message]
2002-10-03 19:33 ` [kbuild-devel] " Sam Ravnborg
2002-10-03 20:01 ` Sam Ravnborg
2002-10-03 20:19 ` Kai Germaschewski
2002-10-03 20:44 ` Sam Ravnborg
2002-10-03 20:20 ` Peter Samuelson
2002-10-03 20:30 ` Sam Ravnborg
2002-10-03 20:38 ` Kai Germaschewski
2002-10-03 20:50 ` Sam Ravnborg
2002-10-04 19:07 ` Sam Ravnborg
2002-10-04 20:17 ` Sam Ravnborg
2002-10-09 0:45 ` [kbuild-devel] " Brendan J Simon
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=20021003212618.A17403@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kai-germaschewski@uiowa.edu \
--cc=kbuild-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®