From: <ckim@etri.re.kr>
To: "'Bin Meng'" <bmeng.cn@gmail.com>,
"'Philippe Mathieu-Daudé'" <philmd@redhat.com>
Cc: 'qemu-devel' <qemu-devel@nongnu.org>,
'qemu-discuss' <qemu-discuss@nongnu.org>
Subject: RE: ninja install on ubuntu 16.04 for qemu-5.2.0 build
Date: Tue, 2 Mar 2021 20:21:28 +0900 [thread overview]
Message-ID: <00aa01d70f56$30c7bf00$92573d00$@etri.re.kr> (raw)
In-Reply-To: <CAEUhbmWxCuJEcGuBVr2K3rzL2tmHeKvGNnwgohc_cUOC=V7eOg@mail.gmail.com>
Hello Bin Meng and Philippe Mathieu-Daudé,
Thanks for the advice. I found apt-get update doesn't help,
But downloading ninja-build source from https://github.com/ninja-build/ninja and
Doing git checkout v1.7.0 and ./configure.py --bootstrap just builds ninja. (I just used v1.7)
Then I renamed /usr/bin/ninja and made a simbolic link to the newly built ninja as /usr/bin/ninja.
And found qemu-5.2.0 is built and runs ok with usual "configure --target-list=aarch64-softmmu" and make -j12 under build directory.
Thanks for the help!
Chan Kim
> -----Original Message-----
> From: Bin Meng <bmeng.cn@gmail.com>
> Sent: Tuesday, March 2, 2021 7:12 PM
> To: Philippe Mathieu-Daudé <philmd@redhat.com>
> Cc: ckim@etri.re.kr; qemu-discuss <qemu-discuss@nongnu.org>; qemu-devel
> <qemu-devel@nongnu.org>
> Subject: Re: ninja install on ubuntu 16.04 for qemu-5.2.0 build
>
> On Tue, Mar 2, 2021 at 6:02 PM Philippe Mathieu-Daudé <philmd@redhat.com>
> wrote:
> >
> > On 3/2/21 10:15 AM, ckim@etri.re.kr wrote:
> > > Hello,
> > >
> > > qemu-5.2.0 now internally uses mesa for building qemu.
> > >
> > > Isn’t there any guideline for this new build method on qemu document
> > > page?( I couldn’t find one).
> > >
> > > I was met with this ‘couldn’t find Ninja 1.7 or newer’ and tried
> > > installing ninja with apt-get but the version is too low.(it seems
> > > it’s 1.5)
> >
> > 1.7.1 is available, maybe try running "apt-get update" first?
> >
> > Package: ninja-build
> > Architecture: amd64
> > Version: 1.7.1-1~ubuntu16.04.1
> > Priority: optional
> > Section: universe/devel
> > Origin: Ubuntu
> > Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
> > Original-Maintainer: Felix Geyer <fgeyer@debian.org>
> > Bugs: https://bugs.launchpad.net/ubuntu/+filebug
> > Installed-Size: 286
> > Depends: libc6 (>= 2.15), libstdc++6 (>= 5.2)
> > Conflicts: ninja
> > Filename:
> > pool/universe/n/ninja-build/ninja-build_1.7.1-1~ubuntu16.04.1_amd64.de
> > b
> > Size: 91424
> > MD5sum: 6384d9c31ca18803e90b7bf3f5c3ab28
> > SHA1: ab64ea16c36a39bbfd6929351fff8e2d5768e801
> > SHA256:
> > 8f8ba3ccb7873cb264bd648437eb8e7d7abd4093254135f6830e368a25512b9f
> > SHA512:
> > 222de7f1dc96979a9d1487f090cd138397b0f6cc935acf99166a5b6d8ba951529d9303
> > 9e6d431b85fa9abaf4285961e643a97dce747e41f76f4b874e1932c25e
> > Homepage: https://ninja-build.org/
> > Description: small build system closest in spirit to Make
> > Description-md5: 5ef1371c63de86fcf36c1ddc875d2f26
> >
> > >
> > > I guess because I’m using ubuntu 16.04 - somewhat old version, I’ll
> > > have to download the ninja and mesa.
> > >
> > > Can someone give me an advice on which is the best way to solve this?
>
> FYI, Ubuntu 16.04 is no longer a supported host.
>
> I am working on Ubuntu 16.04 with a ninja I built from source, and passed
> it to QEMU configure script which works fine.
>
> >
> > An alternative when you can't update the system packages is to use a
> > Docker container (you might need to ask the machine administrator to
> > install it).
> >
>
> Regards,
> Bin
prev parent reply other threads:[~2021-03-02 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <009801d70f44$a75be810$f613b830$@etri.re.kr>
2021-03-02 10:02 ` ninja install on ubuntu 16.04 for qemu-5.2.0 build Philippe Mathieu-Daudé
2021-03-02 10:11 ` Bin Meng
2021-03-02 11:21 ` ckim [this message]
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='00aa01d70f56$30c7bf00$92573d00$@etri.re.kr' \
--to=ckim@etri.re.kr \
--cc=bmeng.cn@gmail.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
/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).