From 9e1c253fe814c85a316520bd6bd258adaa71df79 Mon Sep 17 00:00:00 2001
From: Andrei Vagin <avagin@google.com>
Date: Fri, 3 May 2019 14:11:55 -0700
Subject: gvisor: run bazel in a docker container

bazel has a lot of dependencies and users don't want to install them
just to build gvisor.

These changes allows to run bazel in a docker container.
A bazel cache is on the local file system (~/.cache/bazel), so
incremental builds should be fast event after recreating a bazel
container.

Here is an example how to build runsc:
make BAZEL_OPTIONS="build runsc:runsc" bazel

Change-Id: I8c0a6d0c30e835892377fb6dd5f4af7a0052d12a
PiperOrigin-RevId: 246570877
---
 test/syscalls/linux/pty.cc | 2 ++
 1 file changed, 2 insertions(+)

(limited to 'test/syscalls')

diff --git a/test/syscalls/linux/pty.cc b/test/syscalls/linux/pty.cc
index 0485d187c..f926ac0f9 100644
--- a/test/syscalls/linux/pty.cc
+++ b/test/syscalls/linux/pty.cc
@@ -18,9 +18,11 @@
 #include <sys/ioctl.h>
 #include <sys/mman.h>
 #include <sys/stat.h>
+#include <sys/sysmacros.h>
 #include <sys/types.h>
 #include <termios.h>
 #include <unistd.h>
+
 #include <iostream>
 
 #include "gtest/gtest.h"
-- 
cgit v1.2.3