6fd4699d07
If our own proxy command isn't available for some reason and nc is available, fall back to use it. (From OE-Core rev: aaab6ae94258277dcd2f29823a64689e6245fa7a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
973 B
Executable File
#! /bin/bash
SCRIPTDIR=dirname $0
Check oe-git-proxy-socks exists
PROXYSOCKS=which oe-git-proxy-socks 2> /dev/null
if [ -z "$PROXYSOCKS" -a -e "$SCRIPTDIR/oe-git-proxy-socks.c" ]; then
# If not try and build it
gcc $SCRIPTDIR/oe-git-proxy-socks.c -o $SCRIPTDIR/oe-git-proxy-socks
fi
PROXYSOCKS=which oe-git-proxy-socks 2> /dev/null
if [ ! -x "$PROXYSOCKS" ]; then
# If that fails, we can see if netcat (nc) is available
NETCAT=which nc 2> /dev/null
if [ ! -x "$NETCAT" ]; then
# If that fails, explain to the user
echo "Unable to find oe-git-proxy-socks. This is usually created with the command"
echo "'gcc scripts/oe-git-proxy-socks.c -o scripts/oe-git-proxy-socks' which we tried"
echo "but it doesn't seem to have worked. Please compile the binary manually."
echo "Alternativly, install nc (netcat) on this machine."
exit 1
fi
exec $NETCAT -x $GIT_PROXY_HOST:$GIT_PROXY_PORT "$@"
fi
oe-git-proxy-socks -S $GIT_PROXY_HOST:$GIT_PROXY_PORT $@