On Wed, Jun 10, 2015 at 10:26 AM, Martin Stolpe <martinsto...@gmail.com> wrote: > Problem is that when building binutils using GCC >=5.0 > warnings will be treated as errors which will cause > the build to fail. > > Signed-off-by: Martin Stolpe <martin.sto...@gmail.com> > --- > meta/recipes-devtools/binutils/binutils_2.24.bb | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/meta/recipes-devtools/binutils/binutils_2.24.bb > b/meta/recipes-devtools/binutils/binutils_2.24.bb > index 738aaee..bc34a14 100644 > --- a/meta/recipes-devtools/binutils/binutils_2.24.bb > +++ b/meta/recipes-devtools/binutils/binutils_2.24.bb > @@ -7,12 +7,15 @@ EXTRA_OECONF += "--with-sysroot=/ \ > --enable-install-libbfd \ > --enable-install-libiberty \ > --enable-shared \ > + --disable-werror \ > " > > EXTRA_OECONF_class-native = "--enable-targets=all \ > --enable-64-bit-bfd \ > --enable-install-libiberty \ > - --enable-install-libbfd" > + --enable-install-libbfd \ > + --disable-werror \ > + "
lowering the guards is not the right approach. I understand you want to compile fido with distros that are released after fido. but better would be to backport relevant fixed into component itself. > > do_install_class-native () { > autotools_do_install > -- > 2.4.2 > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core