linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <yiding_wang@agilent.com>
To: <linux-kernel@vger.kernel.org>
Subject: 2.5.x module make questions
Date: Tue, 29 Jul 2003 14:45:35 -0600	[thread overview]
Message-ID: <334DD5C2ADAB9245B60F213F49C5EBCD05D55239@axcs03.cos.agilent.com> (raw)

Team,

I have two questions regarding kbuild.
1, According to doc., makefile can do descending.  Could make carry ascending?
2, Does old style of makefile still work (it should according to the article of "Driver porting: compiling external module")?

I was using "make -C /usr/src/linux SUBDIRS=$PWD modules". Build process at the stage 2 after primary Makefile trying to get secondary Makefile to be involved.  I have fairly complicated source tree to be involved in the module build process, including descending and ascending.  The main (primary) Makefile is almost down to the bottom of the tree. It is in old style and has followng content:

export TOPDIR
export CFLAGS

all : ag.o

ag.o: ../../../../t/s/ts.o ../../../f/c/fc.o ../../../f/i/fi.o  s/sl.o 
	ld -r -o ag.o ../../../../t/s/ts.o ../../../f/c/fc.o ../../../f/i/fi.o s/sl.o 

../../../../t/s/ts.o:
	@echo "Making t-s"
	@make -C ../../../../t/s

../../../f/c/fc.o:
	@echo "Making F-C"
	@make -C ../../../f/c 

../../../f/i/fi.o:
	@echo "Making F-I"
	@make -C ../../../f/i

s/sl.o:
	@echo "Making linux s-l"
	@make -C s 

What happend is the linux make exits after excuting the above Makefile. It did not change the directory "@make -C **" and perform futher make.

At the end of tree, a Makefile is regular like (../../../f/c/Makefile):
T_INC = -I../../../t/api -I../../../t/s 
SL_INC = -I../../d/l/c
FC_INC = -I../i
TI_INC = -I../../d/api
INCLUDE_LOCAL = $(T_INC) $(SL_INC) $(FC_INC) $(TII_INC)

obj-m := fc.o

fc-objs := t1.o t2.o t3.o t4.o

EXTRA_CFLAGS := $(INCLUDE_LOCAL) -I$(TOPDIR)/drivers/scsi

Any suggestion is welcomed.  If the kbuild cannot do ascending, I have to change the source tree structure but that is the least I want to do.

Many thanks!

Eddie
 

             reply	other threads:[~2003-07-29 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 20:45 yiding_wang [this message]
2003-07-29 21:09 ` 2.5.x module make questions Sam Ravnborg
2003-08-11 11:27   ` David Woodhouse
2003-07-29 21:33 yiding_wang

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=334DD5C2ADAB9245B60F213F49C5EBCD05D55239@axcs03.cos.agilent.com \
    --to=yiding_wang@agilent.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).