[meta-intel] [met-intel-quark] Enable stack-protector defense support for SPI image

[Ramajayam, Yugeraj]

Hi Brendan,

I tested by changing LDSO_BASE_FILENAME, it worked. But when I try enable SSP configs, somehow they are not enabled. I already checked for uclibc config dependencies which might block the SSP configs from being enabled, they are clear so far. I will check again thoroughly for any other indirect dependencies.

Im using meta-intel-quark on dizzy branch too.

Regards,
RAJ

> -----Original Message-----
> From: Le Foll, Brendan
> Sent: Friday, July 10, 2015 10:08 PM
> To: Ramajayam, Yugeraj
> Cc: meta-intel at yoctoproject.org
> Subject: Re: [meta-intel] [met-intel-quark] Enable stack-protector defense
> support for SPI image
> 
> On Thu, Jul 09, 2015 at 08:35:43AM +0100, Ramajayam, Yugeraj wrote:
> > 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+48a
> > 0006012-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+48a
> > 0006012-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 ??
> 
> Are you sure you don't have another recipe overriding that config? I gave it a
> quick go changing LDSO_BASE_FILENAME and I can see that change
> propagated in the build tree. I'm using meta-intel-quark on dizzy. What
> metadata are you using?
> 
> Cheers,
> Brendan