Another thing I noticed was the SOCKS_SERVER command did not seem to be exported into bitbake’s environment which could have caused the error. Although I did set SOCKS_SERVER environment in my shell, I’m wondering how do I set the same thing in bitbake so it **might** work?
Chan Kit From: Yu, Chan KitX Sent: Thursday, December 04, 2014 9:46 AM To: Burton, Ross Cc: yocto@yoctoproject.org; yuchan...@gmail.com Subject: RE: [yocto] Issue with compiling x264 package in Yocto Unfortunately, that doesn’t work. I also added poky/scripts/ into PATH so oe-git-proxy is within PATH but no good. So I’m stuck here now getting x264 to git clone ☹ I also added GIT_PROXY_COMMAND to oe-git-proxy but no luck. Chan Kit From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Thursday, December 04, 2014 7:17 AM To: Yu, Chan KitX Cc: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>; yuchan...@gmail.com<mailto:yuchan...@gmail.com> Subject: Re: [yocto] Issue with compiling x264 package in Yocto On 3 December 2014 at 05:40, Yu, Chan KitX <chan.kitx...@intel.com<mailto:chan.kitx...@intel.com>> wrote: Weirdly, git cloning that repository worked marvelously. I’m out of my depth here so I’m posting here so more minds can dig this. I have also attached the full log files so those interested can read the whole error log. I think I have set the SOCKS proxy correctly since git clone works for me but I’m open to suggestions. bitbake clears the environment when starting so its possible that your proxy settings are being lost. I believe setting eg ALL_PROXY="socks://my.proxy/" in your local.conf should work. Ross
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
