From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Chen, Farrah" <farrah.chen@intel.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Hu, Robert" <robert.hu@intel.com>
Subject: Re: [Qemu-devel] qemu compile error
Date: Mon, 23 Oct 2017 14:46:03 +0100 [thread overview]
Message-ID: <20171023134603.GL16472@redhat.com> (raw)
In-Reply-To: <1B925CC0CD9F3341B32D442251E7E1DC39106402@shsmsx102.ccr.corp.intel.com>
On Mon, Oct 23, 2017 at 01:43:30PM +0000, Chen, Farrah wrote:
> 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.
To avoid need to create the wrapper script, I copied you on a patch that
would let you run
./configure --with-git="tsocks git"
As a further alternative, I think it might also be possible to just run
tsocks ./scripts/git-submodule.sh dtc ui/keycodemapdb
immediately after configure, but before running make.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-10-23 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 12:13 [Qemu-devel] qemu compile error Chen, Farrah
2017-10-20 12:41 ` Daniel P. Berrange
2017-10-20 12:41 ` Peter Maydell
2017-10-20 12:45 ` Daniel P. Berrange
2017-10-20 14:42 ` Eric Blake
2017-10-23 13:43 ` Chen, Farrah
2017-10-23 13:46 ` Daniel P. Berrange [this message]
2017-10-24 2:17 ` Chen, Farrah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171023134603.GL16472@redhat.com \
--to=berrange@redhat.com \
--cc=farrah.chen@intel.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).