From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alan Levy <alan.levy@plextek.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: Problem using Subversion in Pyro
Date: Fri, 19 May 2017 10:48:31 +0100 [thread overview]
Message-ID: <1495187311.27342.149.camel@linuxfoundation.org> (raw)
In-Reply-To: <76e10e401a174bdca9f6a65acafbff5e@PLEXTEK-EXCH1.plextek.lan>
On Thu, 2017-05-18 at 14:22 +0000, Alan Levy wrote:
> --limit 1 --no-auth-cache ! http://server/path/my_module/ failed with
> exit code 127, output:
> /usr/bin/env: 'svn': No such file or directory
>
> If I comment out the line containing SRCPV, all is well. Digging into
> the code it appears that svn is missing from ${HOSTTOOLS} in
> bitbake.conf.
I can understand how we end up in this situation.
In general, subversion-native is built before the recipe's do_fetch so
things work.
When you use SRCREV = "${AUTOREV}", it needs subversion at parse time
and its obviously not built it. You therefore need to use the host
version. You can enable that with:
HOSTTOOLS_append = " svn"
in your config. I'm not sure I see any way around that. We don't really
want to require subversion in general, its only needed if you're using
autorev svn recipes.
Obviously we could do with improving the failure messages though...
Cheers,
Richard
next prev parent reply other threads:[~2017-05-19 9:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 14:22 Problem using Subversion in Pyro Alan Levy
2017-05-19 9:48 ` Richard Purdie [this message]
2017-05-19 9:57 ` Alan Levy
2017-05-19 10:09 ` Alexander Kanavin
2017-05-19 12:44 ` Alan Levy
-- strict thread matches above, loose matches on Subject: below --
2017-05-18 11:40 Alan Levy
2017-05-18 12:40 ` Alexander Kanavin
2017-05-18 13:04 ` Alan Levy
2017-05-18 13:14 ` Alexander Kanavin
2017-05-18 13:32 ` Alan Levy
2017-05-18 13:46 ` Alan Levy
2017-05-18 13:47 ` Alexander Kanavin
2017-05-18 14:02 ` Alan Levy
2017-05-18 14:11 ` Alexander Kanavin
2017-05-18 14:24 ` Alan Levy
2017-05-18 13:00 ` 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=1495187311.27342.149.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alan.levy@plextek.com \
--cc=bitbake-devel@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 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.