Bug 2007

Summary:	oe-git-proxy-socks: command not found
Product:	[Build System, Metadata & Runtime] BitBake	Reporter:	Inaky Perez-Gonzalez <inaky.perez-gonzalez>
Component:	bitbake	Assignee:	Richard Purdie <richard.purdie>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Low	CC:	poky.bs.watcher, poky.watcher, sgw
Version:	unspecified
Target Milestone:	1.2
Hardware:	x86
OS:	Multiple
Whiteboard:	Patch posted for review
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Inaky Perez-Gonzalez 2012-02-17 13:05:55 UTC

Build failed with:

| ERROR: Function 'Fetcher failure for URL: 'git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=yocto/standard/common-pc/base,meta;name=machine,meta'. Unable to fetch URL git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=yocto/standard/common-pc/base,meta;name=machine,meta from any source.' failed
| /opt/poky-edison-6.0/scripts/oe-git-proxy-socks-command: line 2: oe-git-proxy-socks: command not found
|  fatal: The remote end hung up unexpectedly
|  fatal: remote origin already exists.
| 

Configuration:

poky-edison-6.0.tar.bz2 extracted to /opt
poky-eglibc-x86_64-x86_64-toolchain-gmae-1.1.tar.bz2 extracted to /

$ cd 
$ source /opt/poky/1.1/environment-setup-x86_64-poky-linux
$ source /opt/poky-edison-6.0/oe-init-build-env build-cc

(in build-cc directory)

$ bitbake -k core-image-minimal

Comment 1 Richard Purdie 2012-02-17 17:25:22 UTC

I'm traveling at the moment at rather jetlagged but I'm guessing that to have seen this error, you must have enabled the code in site.conf?

If so, it says:

# If SOCKS is available run the following command to comple a simple transport
# gcc scripts/oe-git-proxy-socks.c -o oe-git-proxy-socks
# and then share that binary somewhere in PATH, then use the following settings
#GIT_PROXY_HOST = "proxy.example.com"
#GIT_PROXY_PORT = "81"
#export GIT_PROXY_COMMAND = "${COREBASE}/scripts/oe-git-proxy-socks-command"

so did you run:

"gcc scripts/oe-git-proxy-socks.c -o oe-git-proxy-socks" ?

Comment 2 Inaky Perez-Gonzalez 2012-02-17 18:02:04 UTC

You bet I didn't :/ sorry for the spinning of wheels.

May I turn this into a wishlist item? Turn the error message "oe-git-proxy-socks" command onto something that is automagically built and put in the poky tree? Or the message saying the same thing as the doc?

Comment 3 Richard Purdie 2012-02-17 18:32:37 UTC

I'm pleased it was something that simple!

I agree this should be easier. If that binary isn't available I think that script should at least have a go at compiling it itself. The scripts/ directory is now always in PATH so this is probably much easier than it ever would have been. We have some usecases where metadata is on a read-only filesystem but I'm prepared to ignore those in this case (a write failure would clearly indicate that problem).

Comment 4 Richard Purdie 2012-03-02 12:32:50 UTC

Fixed in master in http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=6fd4699d077736c54eb3aa31b62593cc5bd82fdc and the preceding commit.