Hi Brian, I followed as you said. I ran,
1. $ bitbake -c menuconfig uclibc 2. Selected fstack-protector option 3. Copied the .config file from build/tmp-spi/work/i586-poky-linux-uclibc/uclibc/0.9.33+gitAUTOINC+48a0006012-r9/git/.config 4. I replaced ../meta/recipes-core/uclibc/uclibc-git/uClibc.distro with .config and renamed it as uClibc.distro and did a $ bitbake uclibc 5. After compilation, I checked the build/tmp-spi/work/i586-poky-linux-uclibc/uclibc/0.9.33+gitAUTOINC+48a0006012-r9. The Uclibc.distro there is the same as I changed in ../meta/recipes-core/uclibc/uclibc-git/uClibc.distro with all the SSP (stack-protector) related configs built in. 6. But, when I checked .config file at build/tmp-spi/work/i586-poky-linux-uclibc/uclibc/0.9.33+gitAUTOINC+48a0006012-r9/git/.config, the SSP configs are disabled as in my previous build. Somehow the stack-protector features were not passed over to the final .config Is there any other way for me to check if those stack-protector options are enabled ? Or did I missing some steps ?? Regards, RAJ -----Original Message----- From: Le Foll, Brendan Sent: Tuesday, July 7, 2015 12:28 AM To: Ramajayam, Yugeraj Cc: [email protected] Subject: Re: [meta-intel] [met-intel-quark] Enable stack-protector defense support for SPI image On Fri, Jul 03, 2015 at 10:30:09AM +0000, Ramajayam, Yugeraj wrote: > Hi all, > > > I would like to turn on the stack-protector defense feature for my SPI > image build. > > I tried to enable the SSP related configs by referring to > [1]http://git.uclibc.org/uClibc/plain/extra/Configs/Config.in in > meta/recipe-core/uclibc/uclibc-git/uClibc.distro. > > Somehow those configs that I enabled was not passed into the final > build output. > > I hope someone can suggest some idea regarding this issue. Thanks in > advance. I had a quick go with meta-intel-quark and it worked as expected, I modified the config by using: $ bitbake -c menuconfig uclibc Grabed the config file from build/tmp-spi/work/i586-poky-linux-uclibc/uclibc/0.9.33+gitAUTOINC+48a0006012-r9/git/.config and then rebuilt uclibc with that config file. My guess is that you manually modified the config file instead of using menuconfig so it reverted you to the default as there where conflicting options? Cheers, Brendan -- _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
