public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] move link of vmlinux from Makefile to a script
Date: Mon, 19 May 2008 08:42:45 +0100	[thread overview]
Message-ID: <48314B95.76E4.0078.0@novell.com> (raw)
In-Reply-To: <20080518185219.GA777@uranus.ravnborg.org>

>>> Sam Ravnborg <sam@ravnborg.org> 18.05.08 20:52 >>>
>> 
>> I have several times been tempted to move it all to a shell script.
>> What has prevented me to do so has only been:
>> 1) that um has some subtle requirement and therefore redefine the
>>    vmlinux link
>> 2) that last time I reworked this stuff Andrew could not boot one
>>    of his systems and I never figured out why
>> 3) lack of time..
>> 
>> But if someone comes up with a patch that moves all this stuff out
>> of the top-level Makefile I am all open for it.
>
>I gave it a quick try. This is first try and comments are welcome.
>It does not address the um issue - but I think that is doable
>with an additional enviroment variable.
>
>The conditionals around KALLSYMS may be simplified - I just did
>not try to do so.

What I fail to see is how the multi-stage (necessary even without
CONFIG_KALLSYMS_EXTRA_PASS) kallsyms linking is now happening.

>What I like with the patch below is that it is 100 times more
>readable than the Makefile stuff.

Fully agree, and hence I'd favor this for .27 over the simple version
handling fix (which I'd hope to see in .26, and maybe even .25.x).

>The drawback are that we either link or not - we cannot restart
>from the middle of the link. But that it not a real issue.
>
>This patch futhermore remove a debug target to assist in
>kallysms issues - I have not seen it used for a long time
>now.

Is this what I referred to above? If so, I don't think these are just
debug targets...

>And I was also considering removing the extra kallsyms
>pass as I dunnot how usefull it is and for an allyesconfig
>build it take too much time.

I'd vote for it, but would of course think that whoever introduced it
should voice his opinion.

>This patch includes your version simplifactions too allthough
>that is not obvious.

Thanks, Jan


  reply	other threads:[~2008-05-19  8:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <482DCD89.76E4.0078.0@novell.com>
     [not found] ` <20080517125204.GA19741@uranus.ravnborg.org>
2008-05-18 18:52   ` [RFC PATCH] move link of vmlinux from Makefile to a script Sam Ravnborg
2008-05-19  7:42     ` Jan Beulich [this message]
2008-05-19  8:19       ` Sam Ravnborg
2008-05-19  8:35         ` Jan Beulich

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=48314B95.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox