All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alfonso Tamés" <alfonso@tames.com>
To: openembedded-devel@lists.openembedded.org
Subject: Cross canadian gcc configuration
Date: Sun, 14 Dec 2014 01:46:25 -0600	[thread overview]
Message-ID: <548D4051.5080504@tames.com> (raw)

Hi,

I just bitbaked an arm based (freescale) Yocto Master image and 
populated an sdk with -c populate_sdk.

When I try to compile a hello world program with the 
arm-poky-linux-gnueabi-gcc compiler, first I get an error not finding 
<stdio.h>, and when I pass the directory through the -I flag, I get the 
classic"stubs.h:7:29: fatal error: gnu/stubs-soft.h: No such file or 
directory" error which I supposed is being thrown since gcc cross 
canadian is not being configured by default (as my image) hard float.

I noticed in the gcc-cross-canadian.inc that the --with-gxx-include-dir 
and --with-sysroot in EXTRA_OECONF_PATHS have a "/not/exist" string:

EXTRA_OECONF_PATHS = "\
--with-gxx-include-dir=/not/exist${target_includedir}/c++/${BINV} \
--with-build-time-tools=${STAGING_DIR_NATIVE}${prefix_native}/${TARGET_SYS}/bin 
\
--with-sysroot=/not/exist \
--with-build-sysroot=${STAGING_DIR_TARGET} \
"

Shoudn't it be ${SDKPATH} instead of "/not/exist" ?

I think that would resolve not finding the include dirs. Now, for the 
environment not picking a hard float image and producing a 
gcc-cross-canadian accordingly, where should I be looking?

Thanks,

Alfonso




             reply	other threads:[~2014-12-14  7:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-14  7:46 Alfonso Tamés [this message]
2014-12-14 13:30 ` Cross canadian gcc configuration Jacob Kroon
2014-12-14 17:21   ` Alfonso Tamés
2014-12-15  8:52     ` Anders Darander

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=548D4051.5080504@tames.com \
    --to=alfonso@tames.com \
    --cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.