mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
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: Wed, 2 Oct 2002 21:32:29 -0600	[thread overview]
Message-ID: <20021003033229.GC3000@clusterfs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210022153090.10307-100000@chaos.physics.uiowa.edu>

On Oct 02, 2002  21:59 -0500, Kai Germaschewski wrote:
> The build process remains recursive, but it changes the recursion
> from 
> 	make -C subdir
> to
> 	make -f subdir/Makefile
> 
> i.e. the current working directory remains the top dir for all times. So 
> gcc/ld/.. are now called from the topdir, allowing to closer resemble 
> a non-recursive build. Some Makefiles may need a little additional 
> tweaking (in particular arch/*), but generally, the changes required are 
> pretty small.

This is nice, because if you are doing "make -j[n]" you currently get
dumped into the wrong file (or just some non-existent file in the wrong
directory) on build warnings and errors (when compiling under vim/emacs)
because e.g. the "make[1]: entering directory fs/ext3" message was
followed by "make[1]: entering directory fs/msdos", while still
compiling files in fs/ext3.

Granted, this isn't a great reason to change, but it bugs me every
day.

Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/


  reply	other threads:[~2002-10-03  3:29 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 [this message]
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
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=20021003033229.GC3000@clusterfs.com \
    --to=adilger@clusterfs.com \
    --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®