Thank you very much!
I removed "1>/dev/null 2>&1" in scripts/git-submodule.sh and found I can't git 
clone git://git.qemu-project.org/dtc.git without tsocks.
I used Daniel's approach, created the wrapper script called 'git' that runs 
'exec tsocks /usr/bin/git "$@"', it succeeded.
Considering we still need to use bare 'git'  to access our internal repo, so, 
for the time being, I use tsocks to git clone 
git://git.qemu-project.org/dtc.git and git://git.qemu.org/keycodemapdb.git 
first, then modified url in .gitmodules before compiling. It works.


Thanks,
Fan

 
-----Original Message-----
From: Peter Maydell [mailto:[email protected]] 
Sent: Friday, October 20, 2017 8:42 PM
To: Chen, Farrah <[email protected]>
Cc: [email protected]; Hu, Robert <[email protected]>; Daniel P. Berrange 
<[email protected]>
Subject: Re: [Qemu-devel] qemu compile error

On 20 October 2017 at 13:13, Chen, Farrah <[email protected]> wrote:
> Hi,
>
> When I build qemu with commit from aef45d51d1204f3335fb99de6658e0c5612c2b67 
> to the latest one, the following error occurred:
>
> tsocks git clone git://git.qemu.org/qemu.git cd qemu
>
> ./configure --target-list=x86_64-softmmu --enable-kvm --enable-vnc 
> --disable-gtk --enable-libusb --enable-numa --disable-sdl make
>   GEN     config-host.h
>   GIT     dtc
>   GEN     trace/generated-tcg-tracers.h
>   GEN     trace/generated-helpers-wrappers.h
>   GEN     trace/generated-helpers.h
>   GEN     module_block.h
>   GEN     trace/generated-helpers.c
> make: *** [git-submodule-update] Error 1

Dan -- I thought we were going to not have the git-submodule.sh script throw 
away the errors from git, but the version in master still seems to do that...

Fan: this happens because we tried to run a 'git submodule'
command and it failed. If you edit scripts/git-submodule.sh to remove the 
"1>/dev/null 2>&1" part of the 'git submodule update' command line then rerun 
make it should print the error messages from git which will tell you what the 
problem is.

(The fact you needed to say 'tsocks git clone...' on your original command 
suggests to me that the problem is that plain 'git submodule update' can't 
access the git repo.)

thanks
-- PMM

Reply via email to