public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: zaitcev@redhat.com, kaos@ocs.com.au, linux-kernel@vger.kernel.org
Subject: Re: kbuild news
Date: Tue, 8 Oct 2002 16:25:04 -0400	[thread overview]
Message-ID: <20021008162504.B4135@devserv.devel.redhat.com> (raw)
In-Reply-To: <20021008.131100.47229080.davem@redhat.com>; from davem@redhat.com on Tue, Oct 08, 2002 at 01:11:00PM -0700

> Date: Tue, 08 Oct 2002 13:11:00 -0700 (PDT)
> From: "David S. Miller" <davem@redhat.com>

>    From: Pete Zaitcev <zaitcev@redhat.com>
>    Date: Tue, 8 Oct 2002 10:42:40 -0400
>    
>    Let's face it, both btfixup and kallsyms "want" to be the last,
>    so something has to give.
> 
> No, btfixup does not care about anything that will go into
> kallsyms.o, no BTFIXUP objects may appear in kallsyms.
> 
> So btfixup may be next to last just fine.

This is very unfortunate, because it invalidates the workaround
where I moved btfixup to "make image" stage. Unles Kai is willing
to change the way the dependencies are handled, I'm stuck.
I am talking about breaking up this:

$(sort $(vmlinux-objs)): $(SUBDIRS) ;

To make every single object (including head.o) on every other
subdirectory (even benign ones) seems a little fishy.

-- Pete

  reply	other threads:[~2002-10-08 20:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1034070360.25457.linux-kernel2news@redhat.com>
2002-10-08 14:42 ` kbuild news Pete Zaitcev
2002-10-08 20:11   ` David S. Miller
2002-10-08 20:25     ` Pete Zaitcev [this message]
2002-10-06  2:10 Kai Germaschewski
2002-10-07  8:08 ` David S. Miller
2002-10-07 14:22   ` Kai Germaschewski
2002-10-07 14:24     ` David S. Miller
2002-10-07 14:35       ` Kai Germaschewski
2002-10-08  9:39       ` Keith Owens

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=20021008162504.B4135@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=davem@redhat.com \
    --cc=kaos@ocs.com.au \
    --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