From: Grant Edwards <grant.b.edwards@gmail.com>
To: yocto@yoctoproject.org
Subject: SDK missing /usr/include/asm header files
Date: Fri, 11 Jan 2019 09:50:46 -0600 [thread overview]
Message-ID: <20190111155046.GA1920@grante> (raw)
I've built a "poky" SDK for use with a Renesas RZN1 eval board (dual
ARM Cortex-A7 cores), and the toolchain's sysroot seems to be missing
the "asm" header directory. When I try to compile a simple tcp echo
server program I get this:
/home/grante/rzn1d/toolchain/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc --sysroot=/home/grante/rzn1d/toolchain/sysroots/armv7vehf-vfp-poky-linux-gnueabi -march=armv7ve -marm -mfpu=vfp -mfloat-abi=hard -Wall -Werror -std=gnu99 -c tcpecho.c
In file included from /home/grante/rzn1d/toolchain/sysroots/armv7vehf-vfp-poky-linux-gnueabi/usr/include/signal.h:287:0,
from /home/grante/rzn1d/toolchain/sysroots/armv7vehf-vfp-poky-linux-gnueabi/usr/include/sys/wait.h:36,
from tcpecho.c:6:
/home/grante/rzn1d/toolchain/sysroots/armv7vehf-vfp-poky-linux-gnueabi/usr/include/bits/sigcontext.h:30:11: fatal error: asm/sigcontext.h: No such file or directory
# include <asm/sigcontext.h>
^~~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [Makefile:26: tcpecho.o] Error 1
Browsing throught the installed toolchain's sysroot confirms that gcc
is correct: there's no "asm" directory in the sysroot's usr/include
directory (or anywhere else in the toolchain's installation tree).
This is the first time I've tried to build an SDK, so I've probably
done something wrong, but I could use a clue as to what might have
gone wrong...
--
Grant Edwards grant.b.edwards Yow! What's the MATTER
at Sid? ... Is your BEVERAGE
gmail.com unsatisfactory?
next reply other threads:[~2019-01-11 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 15:50 Grant Edwards [this message]
2019-01-11 15:52 ` SDK missing /usr/include/asm header files Burton, Ross
2019-01-11 16:20 ` Grant Edwards
2019-01-11 16:30 ` Burton, Ross
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=20190111155046.GA1920@grante \
--to=grant.b.edwards@gmail.com \
--cc=yocto@yoctoproject.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.