From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Fam Zheng" <famz@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCH] travis: use libgcc-4.8-dev (libgcc-6-dev is not available on Ubuntu 14.04)
Date: Mon, 12 Feb 2018 15:46:50 -0300 [thread overview]
Message-ID: <20180212184650.24039-1-f4bug@amsat.org> (raw)
Travis image is based on Ubuntu Trusty (14.04), since d83414e1fd1 we get:
$ sudo -E \
apt-get -yq --no-install-suggests --no-install-recommends --force-yes \
install \
libaio-dev libattr1-dev libbrlapi-dev libcap-ng-dev libgcc-6-dev \
libgnutls-dev libgtk-3-dev libiscsi-dev liblttng-ust-dev \
libncurses5-dev libnfs-dev libnss3-dev libpixman-1-dev libpng12-dev \
librados-dev libsdl1.2-dev libseccomp-dev libspice-protocol-dev \
libspice-server-dev libssh2-1-dev liburcu-dev libusb-1.0-0-dev \
libvte-2.90-dev sparse uuid-dev
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package libgcc-6-dev
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
Since libgcc-dev is used, Travis jobs take much longer.
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index 0dd5020552..79377c8de0 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -13,7 +13,7 @@ addons:
- libattr1-dev
- libbrlapi-dev
- libcap-ng-dev
- - libgcc-6-dev
+ - libgcc-4.8-dev
- libgnutls-dev
- libgtk-3-dev
- libiscsi-dev
--
2.16.1
next reply other threads:[~2018-02-12 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 18:46 Philippe Mathieu-Daudé [this message]
2018-02-12 23:55 ` [Qemu-devel] [PATCH] travis: use libgcc-4.8-dev (libgcc-6-dev is not available on Ubuntu 14.04) Paolo Bonzini
2018-02-13 11:26 ` Daniel P. Berrangé
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=20180212184650.24039-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=alex.bennee@linaro.org \
--cc=famz@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).