From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: SDK extract errors on master
Date: Fri, 3 Jul 2015 15:56:19 +0100 [thread overview]
Message-ID: <5596A293.8020606@communistcode.co.uk> (raw)
Built an SDK today on 7eb0abc5f4d971d9a511c93cfb2eb52b72e6f228 and when
I tried to install it I got the following error:
Setting it up...ls: cannot access
/home/jack/Work/build/openembedded/sdk/1/x86_64/environment-setup-*: No
such file or directory
I have been messing about with the SDK install path and at one point it
did spew out a load of files installed vs shipped warnings I assume due
to a change of path and it getting upset about it, but since then I
deleted the tmp directory and rebuilt a new SDK without warnings.
However, both acted in the same way.
The SDK then sits without installing, seemingly stuck on: grep
OECORE_NATIVE_SYSROOT, which I assume means it's looking for the
(non-existant) environment file.
Any clues? Is this broken for anyone else?
Cheers,
Jack.
next reply other threads:[~2015-07-03 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 14:56 Jack Mitchell [this message]
2015-07-06 11:35 ` SDK extract errors on master Jack Mitchell
2015-07-06 12:30 ` Jack Mitchell
2015-07-06 15:56 ` Jack Mitchell
2015-07-06 16:07 ` Jack Mitchell
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=5596A293.8020606@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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