From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Discussion Mailing List <yocto@yoctoproject.org>
Subject: Errors when installing SDK
Date: Fri, 08 Aug 2014 10:13:20 -0600 [thread overview]
Message-ID: <53E4F720.4070608@mlbassoc.com> (raw)
I built an SDK (using populate_sdk) from the latest master.
When I tried to install it, I got a ton of errors:
root@Zeus:~# /work/tmp/poky-eglibc-i686-arm-toolchain-1.6+snapshot-20140808.sh
Enter target directory for SDK (default: /opt/poky/1.6+snapshot-20140808):
You are about to install the SDK to "/opt/poky/1.6+snapshot-20140808". Proceed[Y/n]?
Extracting SDK...done
Setting it up...xargs: argument line too long
find: `file' terminated by signal 13
find: `file' terminated by signal 13
...
find: `file' terminated by signal 13
When I looked into this, it's happening in the relocate_sdk.sh script.
Here are the relevant lines (via -D):
+ /opt/poky/1.6+snapshot-20140808/relocate_sdk.sh
+ '[' 0 -ne 0 ']'
+ find /opt/poky/1.6+snapshot-20140808/sysroots/i686-pokysdk-linux -type f -exec file '{}' ';'
+ grep ':.*\(ASCII\|script\|source\).*text'
+ awk -F: '{printf "%s\0", $1}'
+ xargs -0 sed -i -e s:/opt/poky/1.6+snapshot-20140808:/opt/poky/1.6+snapshot-20140808:g
xargs: argument line too long
Since I'm not relocating the SDK, can I just ignore these errors?
Wouldn't it be a bit safer to use 'xargs -n256 ...' to limit the
command line length?
Note: I'm not sure where the 'relocate_sdk.sh' script comes from
or else I'd give it a go myself.
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2014-08-08 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 16:13 Gary Thomas [this message]
2014-08-08 16:57 ` Errors when installing SDK Mark Hatle
2014-08-08 17:11 ` Gary Thomas
2014-08-08 17:29 ` Paul Eggleton
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=53E4F720.4070608@mlbassoc.com \
--to=gary@mlbassoc.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.