[OE-core] [PATCH 2/2] oeqa/buildoptions: check that Fortran code actually cross-compiles

[Richard Purdie]

On Mon, 2019-06-24 at 12:13 +0100, Ross Burton wrote:
> Don't just test that we can build the cross-compiler, but test that it actually
> can cross-compile some Fortran.
> 
> Signed-off-by: Ross Burton <ross.burton at intel.com>
> ---
>  meta/lib/oeqa/selftest/cases/buildoptions.py | 7 ++-----
>  1 file changed, 2 insertions(+), 5 deletions(-)
> 
> diff --git a/meta/lib/oeqa/selftest/cases/buildoptions.py b/meta/lib/oeqa/selftest/cases/buildoptions.py
> index 3ad65b40341..6a5378d3ff6 100644
> --- a/meta/lib/oeqa/selftest/cases/buildoptions.py
> +++ b/meta/lib/oeqa/selftest/cases/buildoptions.py
> @@ -162,17 +162,14 @@ class ArchiverTest(OESelftestTestCase):
>          self.assertTrue((g.glob(src_file_glob) and g.glob(tar_file_glob)), "Couldn't find .src.rpm and .tar.gz files under %s/allarch*/xcursor*" % deploy_dir_src)
>  
>  class ToolchainOptions(OESelftestTestCase):
> -
>      def test_toolchain_fortran(self):
>          """
> -        Test whether we can enable and build fortran and its supporting libraries
> +        Test that Fortran works by building a Hello, World binary.
>          """
>  
>          features = 'FORTRAN_forcevariable = ",fortran"\n'
> -        features += 'RUNTIMETARGET_append_pn-gcc-runtime = " libquadmath"\n'

Please don't remove that. We need to check libquadmath builds.

>          self.write_config(features)
> -
> -        bitbake('gcc-runtime libgfortran')
> +        bitbake('fortran-helloworld')

Doesn't this stop testing libgfortran builds too?

Cheers,

Richard