kbuild news
Quoted 11 lines
From: Keith Owens <[email protected]>
Quoted 9 lines
No, the kallsyms object file would not need to be seen by the btfixup.o generator. It could therefore be done validly as:
1) build .tmp_vmlinux
2) build btfixup.o
3) build kallsyms
4) link final vmlinux image
Quoted 6 lines
Quoted 1 line
The order of #2 and #3 could be transposed and that would be fine too.
Wrong. Anything that changes the address or size of any symbol or section invalidates the kallsyms data. kallsyms must be run on the definitive vmlinux contents, with everything else already included and all sizes must be stable.
Let's face it, both btfixup and kallsyms "want" to be the last, so something has to give.
-- Pete
From: Pete Zaitcev <[email protected]>
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.
Quoted 6 lines
Date: Tue, 08 Oct 2002 13:11:00 -0700 (PDT)
From: "David S. Miller" <[email protected]>From: Pete Zaitcev <[email protected]>
Date: Tue, 8 Oct 2002 10:42:40 -0400
Quoted 7 lines
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