From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: RE: [yocto] hosttools
Date: Mon, 10 Jan 2022 14:23:57 +0000 [thread overview]
Message-ID: <20220110142502.4BF62C433F5@smtp.lore.kernel.org> (raw)
In-Reply-To: <16d997f93df7f3c05b21b62ce66a4ced3ef5a4fc.camel@linuxfoundation.org>
Thank you, this explains/fixes an anomaly I saw while building under Jenkins...
-----Original Message-----
From: Richard Purdie <richard.purdie@linuxfoundation.org>
Sent: Monday, January 10, 2022 8:43 AM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] hosttools
External Email Alert
This email has been sent from an account outside of the BAE Systems network.
Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.
On Mon, 2022-01-10 at 13:21 +0000, Monsees, Steven C (US) via lists.yoctoproject.org wrote:
>
> How does yocto determine the locations/paths to the “hosttools” ?
>
> Is there precedence order established for locating the “hosttools” ?,
> and how would one update the search list so as to pick the tool from a
> different/specific location ?
>
It uses PATH, just like the shell would. You'd adjust PATH to influence it.
Once it is constructed you have to remove the path to cause it to be regenerated.
Cheers,
Richard
parent reply other threads:[~2022-01-10 14:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <16d997f93df7f3c05b21b62ce66a4ced3ef5a4fc.camel@linuxfoundation.org>]
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=20220110142502.4BF62C433F5@smtp.lore.kernel.org \
--to=steven.monsees@baesystems.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@lists.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.