2.6 build oddity...
I'm not sure where to report this....
In some sort of freak accident, I had a .s file in my source tree. Whenever I did a build (make bzImage modules), the build process would:
(1) check out the corresponding .c file
(2) build the .s into the .o
(3) delete the .c file
Which I find odd, because:
(1) It never used the .c file, but checked it out anyway
(2) It _did_ delete the .c file, without using it
Matt
Signature · 7 lines
Matthew Dharm Home: [email protected] Maintainer, Linux USB Mass Storage Driver G: Let me guess, you started on the 'net with AOL, right? C: WOW! d00d! U r leet! -- Greg and Customer User Friendly, 2/12/1999
Quoted 7 lines · Matthew Dharm
I'm not sure where to report this....
In some sort of freak accident, I had a .s file in my source tree. Whenever I did a build (make bzImage modules), the build process would:
(1) check out the corresponding .c file
(2) build the .s into the .o
(3) delete the .c file
I have tried to reproduce this locally (with 2.6 kernel btw). make
make kernel/pid.s
rm kernel/pid.c
And as you tell, the .c file is checked out. But I can here that also the .c file is used when compiling pid.o.
Care to provide a few more details, such as:
- Kernel version
- What file is was
- What SCM you are using (uses bk here)
- Full log of what is happening (off-list is fine)
Sam
Quoted 14 lines
Which I find odd, because:
(1) It never used the .c file, but checked it out anyway
(2) It _did_ delete the .c file, without using itMatt
Signature · 7 lines
Matthew Dharm Home: [email protected] Maintainer, Linux USB Mass Storage Driver G: Let me guess, you started on the 'net with AOL, right? C: WOW! d00d! U r leet! -- Greg and Customer User Friendly, 2/12/1999