From: Fred Lamer <fred@rogue-research.com>
To: bitbake-devel@lists.openembedded.org, poky@yoctoproject.org
Subject: CVS support on Yocto 2.3 (Pyro) and bitbake 1.34
Date: Fri, 04 Aug 2017 14:06:01 -0000 [thread overview]
Message-ID: <e380fe57-2ad0-787d-1ea0-b02411480121@rogue-research.com> (raw)
Hi,
I'm trying to bring a project from Yocto 2.1 (Krogoth) to 2.3 (Pyro). I
have a problem with one of my recipe that tries to fetch from a cvs
repository. The recipe work perfectly on Yocto 2.1 (using bitbake 1.30),
but not on Yocto 2.3 (using bitbake 1.34).
It seems like 'cvs' is not installed on the host system? I get the
following error:
********************************************************************************************************************************************************
Fetcher failure: Fetch command export
PATH="/media/yocto/yocto-vetrobot-next.git/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/media/yocto/yocto-vetrobot-next.git/poky/scripts:/media/yocto/yocto-vetrobot-next.git/build/tmp/work/corei7-64-poky-linux/libev/4.15-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/media/yocto/yocto-vetrobot-next.git/build/tmp/work/corei7-64-poky-linux/libev/4.15-r0/recipe-sysroot/usr/bin/crossscripts:/media/yocto/yocto-vetrobot-next.git/build/tmp/work/corei7-64-poky-linux/libev/4.15-r0/recipe-sysroot-native/usr/sbin:/media/yocto/yocto-vetrobot-next.git/build/tmp/work/corei7-64-poky-linux/libev/4.15-r0/recipe-sysroot-native/usr/bin:/media/yocto/yocto-vetrobot-next.git/build/tmp/work/corei7-64-poky-linux/libev/4.15-r0/recipe-sysroot-native/sbin:/media/yocto/yocto-vetrobot-next.git/build/tmp/work/corei7-64-poky-linux/libev/4.15-r0/recipe-sysroot-native/bin:/media/yocto/yocto-vetrobot-next.git/poky/bitbake/bin:/media/yocto/yocto-vetrobot-next.git/build/tmp/hosttools";
export HOME="/home/fred"; /usr/bin/env cvs
'-d:pserver:anonymous@cvs.schmorp.de:/schmorpforge' co -r rel-4_15 libev
failed with exit code 127, output:
/usr/bin/env: ‘cvs’: No such file or directory
********************************************************************************************************************************************************
So, it seems like cvs is either not installed or not in the PATH. Anyone
ever had this problem?
Note that this if I copy/paste this command outside of the bitbake
environnement:
************************************************************************************************
/usr/bin/env cvs '-d:pserver:anonymous@cvs.schmorp.de:/schmorpforge' co
-r rel-4_15 libev
************************************************************************************************
it works perfectly (so it's not a fetch error from the repo).
Thanks
Fred
next reply other threads:[~2017-08-04 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 14:06 Fred Lamer [this message]
2017-09-01 15:44 ` CVS support on Yocto 2.3 (Pyro) and bitbake 1.34 Peter Kjellerstedt
2017-09-01 15:44 ` [bitbake-devel] " Peter Kjellerstedt
2017-09-01 22:03 ` [poky] " akuster808
2017-09-01 22:03 ` [bitbake-devel] " akuster808
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=e380fe57-2ad0-787d-1ea0-b02411480121@rogue-research.com \
--to=fred@rogue-research.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=poky@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.