[yocto] Openembedded/yocto bitbake with gcc 4.8.2 crashes at do_compile elfutils

[Nick Krause]

On Mon, Mar 9, 2015 at 4:35 AM, Everhard Ros <everhard.ros at outlook.com> wrote:
> Hello guys,
>
> I'm trying to run bitbake to get a linux image on an altera Cyclone 5
> devboard(SoCrates). The end goal is to get a linux image that has the OpenCV
> library installed. I'm using the altera version of the yocto project.
>
> Currently everything is running fairly well on ubuntu 12.04.
> When I try to run this bitbake process on CentOS 7, I get the following
> error:
>
> Error: argument to 'sizeof' in 'snprintf' call is the same expression as the
> destination; did you mean to provide an explicit length?
> [-Werror=sizeof-pointer-memaccess]
>
> cc1: all warnings being treated as errors
>
> After some googling here and there, I kind of found the 'bug'.(new gcc has
> this new flag that older versions didn't have which causes a warning and an
> error with -wall).
>
> So now I'm looking for the place where flags are passed to the gcc compiler:
> I tried doing this in the bitbake.conf file in the meta -layer;
> TOOLCHAIN_OPTIONS, BUILD_CFLAGS and TARGET_CFLAGS are now empty.
> In the manual they mention these flags are being sent to the compiler.
>
> I also checked out the elfutils and gcc folders in yocto/meta/devtools/, but
> couldn't find anything relevant there (I used find/grep and the GUI,
> searching for the flags mentioned)
>
>
> Changing the flags in the bitbake.conf file didn't help; do you guys happen
> to have any idea where the compiler flags are being set when bitbake
> executes the do_compile task for elfutils?
>
> Thank you in advance.
>
> cheers!
>
>
>
> P.S: This is a cross-post from this thread I made at linuxquestions.org
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
Did you look for the bb recipe file for elfutils as I am pretty
certain that you can put your gcc compiler flags to work around this
issue inside
that particular bitbake recipe file.
Nick