Hmm. Check the V=1 make output to see that the lparmap.c really got
the -g0.
The log says it didn't. Oops! It looks like the patch that got
committed is
the one that sets CFLAGS_lparmap.s, but really it needs to set
CFLAGS_lparmap.o instead (go kbuild). Did I post the wrong one?
(It's only
one letter different.) Sorry about that!
But there is no lparmap.o! lparmap.s is the generated file.
Maybe the best fix is
$(obj)/lparmap.s: CFLAGS += -g0
This whole, erm, "cleverness" will go away soon fwiw.
Segher
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
