From: "Sid Price" <sidprice@softtools.com>
To: "'Christopher Larson'" <clarson@kergoth.com>, <yocto@yoctoproject.org>
Subject: Re: environment setup script
Date: Thu, 14 Apr 2016 11:54:20 -0600 [thread overview]
Message-ID: <009b01d19676$acd9d780$068d8680$@softtools.com> (raw)
In-Reply-To: <CABcZANkVC3qdywVZedFTNzgADnUB24SEJBKSdNHV85SGRH2jjA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
On Thu, Apr 14, 2016 at 10:39 AM Sid Price <sidprice@softtools.com <mailto:sidprice@softtools.com> > wrote:
Hello, I am new to Yocto and relatively new to Linux. I am working my way through the “Getting Started” guide and I have met a problem. I am trying to run the “environment-setup …” script for the arm platform. First I notice that when I list the folder /opt/poky/2.0.1 I see the scripts but they are not shown as executable. Is this correct? When I try the following command I am told “Permission denied”:
/opt/poky/2.0.1/environment-setup-armv5e-poky-linux-gnueabi
If I use sudo I see “command not found”
The setup script has to be *sourced* into your shell, not run. The instructions most likely included a leading '.' but you missed it. Either type '. /opt/poky/2.0.1/environment-setup-armv5e-poky-linux-gnueabi' or 'source /opt/poky/2.0.1/environment-setup-armv5e-poky-linux-gnueabi' in your shell.
Using “source /opt/poky/2.0.1/environment-setup-armv5e-poky-linux-gnueabi” appeared to work, no errors reported. Should I now expect to see new environment variables when I use “printenv”, because I don’t see any of those mentioned in the getting started guide.
Sid
[-- Attachment #2: Type: text/html, Size: 3952 bytes --]
next prev parent reply other threads:[~2016-04-14 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 17:31 environment setup script Sid Price
2016-04-14 17:42 ` Christopher Larson
2016-04-14 17:54 ` Sid Price [this message]
2016-04-14 17:57 ` Sid Price
2016-04-14 17:44 ` Charles Krinke
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='009b01d19676$acd9d780$068d8680$@softtools.com' \
--to=sidprice@softtools.com \
--cc=clarson@kergoth.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.