public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Chris Wedgwood <cw@f00f.org>, Oleg Verych <olecom@flower.upol.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
	davej@redhat.com, Eric Sandeen <sandeen@sandeen.net>
Subject: Re: [RFC PATCH] Add a 'minimal tree install' target
Date: Thu, 13 Sep 2007 21:19:38 +0200	[thread overview]
Message-ID: <20070913191938.GD27146@uranus.ravnborg.org> (raw)
In-Reply-To: <20070913185753.GA9259@puku.stupidest.org>

Hi Chris.

Thanks for working on this.
 
> > > +if [ "$srctree" != "$objtree" ] ; then
> > > +    cp --parents $(find -type f -name "Makefile*" -o -name "Kconfig*" -not -ipath "$objtree/*Makefile" ) ${tgtdir}
> >                                                                                                ^
> > Why this wildcard??? (objtree/>*<Makefile)
> > Seems to be a typing error.
> 
> no, it's so we catch things like
> 
> linux/build/Makefile
> 
>  *and*
> 
> linux/build/foo/bar/Makefile
Obviously - I missed the find when I looked.
Thanks for the explanation. And no comments needed in the script -
I should just have read the full command line.

> 
> > > +#rm -rf ${tgtdir}/Documentation
> > Remove this line since it is commented out
> 
> right, actually, it can be uncommented but the 'make help' fails; i'm
> not sure if we need make help to work since most of the other targets
> won't anyhow
> 
> so should i remove it (leaving 'make help' as usable) or remove it?
Un-comment it so we do not break make help.

> > Something less hardcoded are preferred. Maybe like:
> > cp -a `ls | grep -v ^asm` asm-generic $(tgtdir}/include
> 
> ok (though i'm not a big fan of ls | grep as a rule, it tends to be
> fragile when people do dumb things)

find . -maxdepth 1 -! -name 'asm*'
seems to do the trick and it is better than ls.

> 
>     sed -n "s/^ALTARCH[[:space:]]:=[[:space:]]\(.*$\)\+/\1/p"
> 
> (i'm sure there is a better way though)

Oleg (added to mail) - you are quite confident in sed et al.
Let us know if there is a simpler way.

(We want to pick i386 from include/asm-x86_64/Kbuild
and similar for the architectures that uses ARCHDEF).

	Sam

  reply	other threads:[~2007-09-13 19:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 23:25 [RFC PATCH] Add a 'minimal tree install' target Chris Wedgwood
2007-09-13 18:34 ` Sam Ravnborg
2007-09-13 18:37   ` Robert P. J. Day
2007-09-13 19:26     ` Sam Ravnborg
2007-09-14  9:59       ` Tilman Schmidt
2007-09-13 18:57   ` Chris Wedgwood
2007-09-13 19:19     ` Sam Ravnborg [this message]
2007-09-13 20:17       ` Oleg Verych
2007-09-13 20:05         ` Chris Wedgwood
2007-09-14 10:04           ` Oleg Verych
2007-09-13 23:27     ` Dave Jones
2007-09-14 16:44 ` Goswin von Brederlow

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=20070913191938.GD27146@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=cw@f00f.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olecom@flower.upol.cz \
    --cc=sandeen@sandeen.net \
    /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