public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Juro Bystricky <juro.bystricky@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] MIPS tune mips64-n32
Date: Mon, 29 Aug 2016 15:45:35 -0700	[thread overview]
Message-ID: <1472510736-3148-1-git-send-email-juro.bystricky@intel.com> (raw)

This patch fixes the issue where a mips CPP compiler configured with n32
cannot find c++ include files:

#include <bits/c++config.h>
int main()
{
    return 0;
}

error: bits/c++config.h: No such file or directory
|  #include <bits/c++config.h>

Although the file c++config.h does exist, CPP cannot find it
as the file is not in the directory CPP expects it to be in.
The fix consists of creating a symlink with the name the directory
CPP expects and point it to the location where the  CPP files
actualy reside.

The patch was tested with two configurations, single compiler
and multilib (both of which used to fail the testsdk):

MACHINE="qemumips64"
require conf/multilib.conf
MULTILIBS = "multilib:lib64 multilib:lib32"
DEFAULTTUNE = "mips64-n32"
DEFAULTTUNE_virtclass-multilib-lib64 = "mips64"
DEFAULTTUNE_virtclass-multilib-lib32 = "mips32r2"
USER_CLASSES += " testsdk "

bitbake core-image-minimal -c populate_sdk
bitbake core_image_minimal -c testsdk

MACHINE="qemumips64"
DEFAULTTUNE = "mips64-n32"
USER_CLASSES += " testsdk "

bitbake core-image-minimal -c populate_sdk
bitbake core_image_minimal -c testsdk


Juro Bystricky (1):
  gcc-runtime.inc: add CPP support for mips64-n32 tune

 meta/recipes-devtools/gcc/gcc-runtime.inc | 10 ++++++++++
 1 file changed, 10 insertions(+)

-- 
2.7.4



             reply	other threads:[~2016-08-29 22:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 22:45 Juro Bystricky [this message]
2016-08-29 22:45 ` [PATCH 1/1] gcc-runtime.inc: add CPP support for mips64-n32 tune Juro Bystricky
2016-08-30  2:24   ` Mark Hatle
2016-08-30 15:47     ` Bystricky, Juro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1472510736-3148-1-git-send-email-juro.bystricky@intel.com \
    --to=juro.bystricky@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox