[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] qemu make

From: lizhuoyao
Subject: Re: [Qemu-discuss] qemu make
Date: Fri, 27 Apr 2018 17:06:47 +0800 (GMT+08:00)

Thanks hearing from you!
your reply clears my confusion completely!

 Have a good day

 > -----原始邮件-----
> 发件人: Peter Maydell <address@hidden>
> 发送时间: 2018年4月26日 星期四
> 收件人: "李卓瑶" <address@hidden>
> 抄送: qemu-discuss <address@hidden>, shengyizju <address@hidden>
> 主题: Re: [Qemu-discuss] qemu make
> On 26 April 2018 at 08:36, 李卓瑶 <address@hidden> wrote:
> > hi:
> >   i get the qemu from git.qemu.org, there is a problem in compiling code,
> >               ui/input-keymap-linux-to-qcode.c: no such file or directory
> That indicates that you don't have the git submodules for some reason.
> Some common reasons for this are:
>  (1) you got a tarball from github -- these are broken but we have no
>  way to configure github not to provide them, unfortunately
>  (2) you used 'git archive' or something to create a tarball --
>  that won't work (if you really need to do it for a test workflow
>  of some kind then scripts/archive-source.sh may help, but almost
>  all users should not need to do this)
>  (3) make was unable to fetch the git submodules for some reason
>  (did it print an error message about this, perhaps a bit further
>  up in the output from the 'no such file or directory' error you
>  quote? If you need to run git via some sort of proxy for it to be
>  able to talk to the git server then this can go wrong, but it
>  should print an error which tells you about this.)
> You should either (1) do a proper git clone of git.qemu.org and
> build from that or (2) use the release tarballs from qemu.org:
> https://www.qemu.org/download/
> Diagnosis process:
>  (1) do you have a .git/ in your source directory?
>  (2) do you have a ui/keycodemapdb/README in your source directory?
> If both 1 and 2 are no:
>  * you're building from an invalid tarball; get the right one and try again
> If 1 is yes but 2 is no:
>  * maybe "get the git submodules" failed -- look for errors in the
> configure or make output
> If 2 is yes:
>  * the build should have succeeded, so something more complicated is wrong
> thanks
> -- PMM

reply via email to

[Prev in Thread] Current Thread [Next in Thread]