Quoting Navdeep Parhar <nparhar_at_gmail.com> (from Wed, 14 Apr 2010 01:33:29 -0700): > I read the UPDATING entry that accompanied r206082 and added WITH_CTF=yes to > my kernel config, hoping to get CTF information in the kernel and all > modules. No luck. > It appears that NO_CTF remains set to 1 inspite of the undef NO_CTF in > various .mk files > and ctfconvert never runs. This is the output I get in my kernel build directory: ---snip--- # make -V NO_CTF -V WITH_CTF yes ---snip--- > I built the kernel with a "make -j16 buildkernel" in /usr/src. How do you determine if ctfconvert is run or not? If you expect to see ctfconvert lines in the build output: this will not be the case, no matter if you enable it or not. With the current way of handling it, I'm not aware of a way how to print the command when ctfconvert is really executed (we can maybe add an echo which prints out something, but the question is if this is worth the effort). You can run objdump -f <objectfile> and have a look if the .SUNW_ctf section is there to determine if CTF stuff was inserted or not. Bye, Alexander. -- http://www.Leidinger.net Alexander _at_ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild _at_ FreeBSD.org : PGP ID = 72077137 The Force is what holds everything together. It has its dark side, and it has its light side. It's sort of like cosmic duct tape.Received on Wed Apr 14 2010 - 07:16:11 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:02 UTC