* CVS support on Yocto 2.3 (Pyro) and bitbake 1.34
@ 2017-08-04 14:06 Fred Lamer
2017-09-01 15:44 ` [bitbake-devel] " Peter Kjellerstedt
0 siblings, 1 reply; 5+ messages in thread
From: Fred Lamer @ 2017-08-04 14:06 UTC (permalink / raw)
To: bitbake-devel, poky
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: CVS support on Yocto 2.3 (Pyro) and bitbake 1.34
2017-08-04 14:06 CVS support on Yocto 2.3 (Pyro) and bitbake 1.34 Fred Lamer
@ 2017-09-01 15:44 ` Peter Kjellerstedt
0 siblings, 0 replies; 5+ messages in thread
From: Peter Kjellerstedt @ 2017-09-01 15:44 UTC (permalink / raw)
To: Fred Lamer, bitbake-devel, poky
> -----Original Message-----
> From: bitbake-devel-bounces@lists.openembedded.org [mailto:bitbake-
> devel-bounces@lists.openembedded.org] On Behalf Of Fred Lamer
> Sent: den 4 augusti 2017 16:00
> To: bitbake-devel@lists.openembedded.org; poky@yoctoproject.org
> Subject: [bitbake-devel] CVS support on Yocto 2.3 (Pyro) and bitbake
> 1.34
>
> 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
This is due to the introduction of the HOSTTOOLS and HOSTTOOLS_NONFATAL
variables in Pyro. Only executables included in these variables will be
available from the host environment when bitbake is running. The
executables in HOSTTOOLS must exist or bitbake will abort. The executables
in HOSTTOOLS_NONFATAL will be available if they exist.
So if you add cvs to HOSTTOOLS_NONFATAL, using cvs to fetch a repository
should start to work again.
//Peter
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [bitbake-devel] CVS support on Yocto 2.3 (Pyro) and bitbake 1.34
@ 2017-09-01 15:44 ` Peter Kjellerstedt
0 siblings, 0 replies; 5+ messages in thread
From: Peter Kjellerstedt @ 2017-09-01 15:44 UTC (permalink / raw)
To: Fred Lamer, bitbake-devel, poky
> -----Original Message-----
> From: bitbake-devel-bounces@lists.openembedded.org [mailto:bitbake-
> devel-bounces@lists.openembedded.org] On Behalf Of Fred Lamer
> Sent: den 4 augusti 2017 16:00
> To: bitbake-devel@lists.openembedded.org; poky@yoctoproject.org
> Subject: [bitbake-devel] CVS support on Yocto 2.3 (Pyro) and bitbake
> 1.34
>
> 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
This is due to the introduction of the HOSTTOOLS and HOSTTOOLS_NONFATAL
variables in Pyro. Only executables included in these variables will be
available from the host environment when bitbake is running. The
executables in HOSTTOOLS must exist or bitbake will abort. The executables
in HOSTTOOLS_NONFATAL will be available if they exist.
So if you add cvs to HOSTTOOLS_NONFATAL, using cvs to fetch a repository
should start to work again.
//Peter
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [poky] CVS support on Yocto 2.3 (Pyro) and bitbake 1.34
2017-09-01 15:44 ` [bitbake-devel] " Peter Kjellerstedt
@ 2017-09-01 22:03 ` akuster808
-1 siblings, 0 replies; 5+ messages in thread
From: akuster808 @ 2017-09-01 22:03 UTC (permalink / raw)
To: Peter Kjellerstedt, Fred Lamer, bitbake-devel, poky
On 09/01/2017 08:44 AM, Peter Kjellerstedt wrote:
>> -----Original Message-----
>> From: bitbake-devel-bounces@lists.openembedded.org [mailto:bitbake-
>> devel-bounces@lists.openembedded.org] On Behalf Of Fred Lamer
>> Sent: den 4 augusti 2017 16:00
>> To: bitbake-devel@lists.openembedded.org; poky@yoctoproject.org
>> Subject: [bitbake-devel] CVS support on Yocto 2.3 (Pyro) and bitbake
>> 1.34
>>
>> 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
> This is due to the introduction of the HOSTTOOLS and HOSTTOOLS_NONFATAL
> variables in Pyro. Only executables included in these variables will be
> available from the host environment when bitbake is running. The
> executables in HOSTTOOLS must exist or bitbake will abort. The executables
> in HOSTTOOLS_NONFATAL will be available if they exist.
Is this supported in Master? I could not find it for a backport
consideration.
- armin
>
> So if you add cvs to HOSTTOOLS_NONFATAL, using cvs to fetch a repository
> should start to work again.
>
> //Peter
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [bitbake-devel] CVS support on Yocto 2.3 (Pyro) and bitbake 1.34
@ 2017-09-01 22:03 ` akuster808
0 siblings, 0 replies; 5+ messages in thread
From: akuster808 @ 2017-09-01 22:03 UTC (permalink / raw)
To: Peter Kjellerstedt, Fred Lamer, bitbake-devel, poky
On 09/01/2017 08:44 AM, Peter Kjellerstedt wrote:
>> -----Original Message-----
>> From: bitbake-devel-bounces@lists.openembedded.org [mailto:bitbake-
>> devel-bounces@lists.openembedded.org] On Behalf Of Fred Lamer
>> Sent: den 4 augusti 2017 16:00
>> To: bitbake-devel@lists.openembedded.org; poky@yoctoproject.org
>> Subject: [bitbake-devel] CVS support on Yocto 2.3 (Pyro) and bitbake
>> 1.34
>>
>> 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
> This is due to the introduction of the HOSTTOOLS and HOSTTOOLS_NONFATAL
> variables in Pyro. Only executables included in these variables will be
> available from the host environment when bitbake is running. The
> executables in HOSTTOOLS must exist or bitbake will abort. The executables
> in HOSTTOOLS_NONFATAL will be available if they exist.
Is this supported in Master? I could not find it for a backport
consideration.
- armin
>
> So if you add cvs to HOSTTOOLS_NONFATAL, using cvs to fetch a repository
> should start to work again.
>
> //Peter
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-09-01 22:03 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-08-04 14:06 CVS support on Yocto 2.3 (Pyro) and bitbake 1.34 Fred Lamer
2017-09-01 15:44 ` 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
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.