summaryrefslogtreecommitdiff
path: root/meta/recipes-kernel/kern-tools
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2013-12-05 00:48:30 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-12-05 12:32:11 +0000
commita5e7ee5770b9e0cf719c573efffd874440f74289 (patch)
treeb43c144b36c797bb760ddb6cc6f6b711c6d50276 /meta/recipes-kernel/kern-tools
parent162cfffb32d909f9cac88b4f872173d21524d8ed (diff)
downloadopenembedded-core-a5e7ee5770b9e0cf719c573efffd874440f74289.tar.gz
openembedded-core-a5e7ee5770b9e0cf719c573efffd874440f74289.tar.bz2
openembedded-core-a5e7ee5770b9e0cf719c573efffd874440f74289.zip
gcc: Allow fortran to build successfully in 4.8
gcc 4.8 fortran presents some challenges: * libquadmath headers need to be in the libexec include dir. It turns out to be easiest just to manually do this. * libgfortran configure needs libquadmath to be compiled. This means a separate recipe is needed (the alternative is gross hacks) * the libtool uses to link libgfortran doesn't have our improved rpath handling and puts bogus RPATHS into the libraries. We can avoid this by tweaking libtool with sed. This patch resolves those issues. Any user of fortran does need to DEPEND on libgfortran in order to trigger it to build but this shouldn't be a major issue. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-kernel/kern-tools')
0 files changed, 0 insertions, 0 deletions