Re: [PATCH 27/56] node/GET: use wget -c

[Geraldo Netto]

Hello Waldek/Friends,

Don't mind, I'll review those patches too!
Must say, I'm trying big things first because it sounds more exciting :)


Kind Regards,

Geraldo Netto
Sapere Aude => Non dvcor, dvco
http://exdev.sf.net/

On 18 February 2018 at 00:09, Waldek Kozaczuk  wrote:

> Cannot apply this patch:
>
> Applying: node/GET: use wget -c
> error: patch failed: node/GET:10
> error: node/GET: patch does not apply
> Patch failed at 0001 node/GET: use wget -c
> The copy of the patch that failed is found in:
> /home/wkozaczuk/projects/osv/.git/modules/apps/rebase-apply/patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
>
> On Tuesday, January 16, 2018 at 2:44:35 PM UTC-5, Geraldo Netto wrote:
>>
>> Signed-off-by: geraldo netto 
>> ---
>>  node/GET | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/node/GET b/node/GET
>> index 79a3b27..142ae4f 100755
>> --- a/node/GET
>> +++ b/node/GET
>> @@ -10,6 +10,6 @@ then
>>exit 1
>>  fi
>>
>> -wget "https://github.com/nodejs/node/archive/v${1}.tar.gz; -O - | tar
>> zxf -
>> +wget -c "https://github.com/nodejs/node/archive/v${1}.tar.gz; -O - |
>> tar zxf -
>>
>>  ./patch "$1"
>> --
>> 2.7.4
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "OSv Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to osv-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: mysql: failed looking up symbol numa_all_nodes_ptr

[Geraldo Netto]

Hello Nadav/All,

My Friends, I have made some progress here
Apparently, the unit test for crypt.h is okay and MySQL is now complaining
only about libnuma.so.1 which I can copy from my local machine as Nadav
pointed out
BTW, MySQL usr.manifest is using ":" instead of ": ", but one fix at a time
:)

netto@vmx01 ~/osv $ scripts/run.py -V
OSv v0.24-500-g6828ed0
2 CPUs detected
Firmware vendor: SeaBIOS
bsd: initializing - done
VFS: mounting ramfs at /
VFS: mounting devfs at /dev
net: initializing - done
vga: Add VGA device instance
eth0: ethernet address: 52:54:00:12:34:56
virtio-blk: Add blk device instances 0 as vblk0, devsize=10737418240
random: virtio-rng registered as a source.
random:  initialized
VFS: unmounting /dev
VFS: mounting zfs at /zfs
zfs: mounting osv/zfs from device /dev/vblk0.1
random: device unblocked.
VFS: mounting devfs at /dev
VFS: mounting procfs at /proc
program zpool.so returned 1
BSD shrinker: event handler list found: 0xa17a0500
BSD shrinker found: 1
BSD shrinker: unlocked, running
[I/42 dhcp]: Broadcasting DHCPDISCOVER message with xid: [1962368973]
[I/244 dhcp]: Received DHCPOFFER message from DHCP server: 192.168.122.1
regarding offerred IP address: 192.168.122.15
[I/244 dhcp]: Broadcasting DHCPREQUEST message with xid: [1962368973] to
SELECT offered IP: 192.168.122.15
[I/244 dhcp]: Received DHCPACK message from DHCP server: 192.168.122.1
regarding offerred IP address: 192.168.122.15
[I/244 dhcp]: Server acknowledged IP 192.168.122.15 for interface eth0 with
time to lease in seconds: 86400
eth0: 192.168.122.15
[I/244 dhcp]: Configuring eth0: ip 192.168.122.15 subnet mask 255.255.255.0
gateway 192.168.122.1 MTU 1500
[I/42 dhcp]: Waiting for IP...
could not load libnuma.so.1
/usr/bin/mysqld: failed looking up symbol numa_all_nodes_ptr

[backtrace]
0x0033e303 
0x0038ca14 
0x0033c6a4 
0x0033f107 
0x00342412
,
std::vector, std::allocator > >,
std::vector >&)+1602>
0x00342c52
,
std::vector, std::allocator > >)+322>
0x004144c3
 const&,
std::vector, std::allocator > > const&, bool,
std::unordered_map, std::__cxx11::basic_string,
std::hash >, std::equal_to >,
std::allocator const,
std::__cxx11::basic_string > > > const*)+707>
0x00414c08  const&,
std::vector, std::allocator > > const&, bool,
std::unordered_map, std::__cxx11::basic_string,
std::hash >, std::equal_to >,
std::allocator const,
std::__cxx11::basic_string > > > const*)+104>
0x00414e1b
,
std::allocator > > const&)+27>
0x00213a49 
0x00444eb5 
0x003e5d76 
0x00388f82 


Kind Regards,

Geraldo Netto
Sapere Aude => Non dvcor, dvco
http://exdev.sf.net/

On 11 February 2018 at 07:24, Nadav Har'El  wrote:

>
> On Sat, Feb 10, 2018 at 7:31 AM, Geraldo Netto 
> wrote:
>
>> Dear Friends,
>>
>> I was trying to 

Re: [PATCH] explicitly tell at README.md that compilation requires at least 2GB of RAM

[Geraldo Netto]

Hello Nadav/All,

I see, well, I have not set any jobs which means it is equivalent to -j1
As for the building, I was not running any other software, just make
and the ssh (connected over putty)
As you deduced, I didn't setup a swap (otherwise the performance would
be horrible here, still using old disks here)

Maybe we could change the approach and just print a warning that 2 GB
of RAM and 3 GB of disk is recommended?


Kind Regards,

Geraldo Netto
Sapere Aude => Non dvcor, dvco
http://exdev.sf.net/

On 22 February 2018 at 05:38, Nadav Har'El  wrote:
>
> On Thu, Feb 22, 2018 at 6:02 AM, geraldo netto 
> wrote:
>>
>> this will avoid people having such situation below:
>> ...
>>   CXX core/commands.cc
>> virtual memory exhausted: Cannot allocate memory
>
>
> I'm not comfortable with saying just that "2 GB of memory is needed for the
> compilation". What is this number based on? For example, it strongly depends
> on how much compilation you do in parallel, e.g., if "make -j4" doesn't
> work, because it compiles 4 source files in parllel, probably "make -j1"
> would. What "-j" option did you try? Also the amount of memory you need also
> depends on what else you have running on your machine - and whether you have
> swap (I guess you had none).
>
> Nobody would set up a physical host today with just 1 GB of memory. A local
> shop here which I recently went to sells its most basic setups with 4 GB.
> And if you set up a VM with just 1 GB of memory and no swap, isn't it
> obvious that if you get errors like "virtual memory exhausted" you need to
> increase your memory?
>
> By the way, something which is more deterministic and perhaps more
> surprising that memory usage is the build's disk usage. Users should have at
> least 3 GB of free disk space, because of some surprising disk usage of the
> git files (700 MB) and the "external" directory (1.2 GB).
>
>>
>> make: *** [build/release.x64/core/commands.o] Error 1
>> Makefile:363: recipe for target 'build/release.x64/core/commands.o' failed
>> make failed. Exiting from build script
>>
>> VM configuration:
>> VMWare player
>> 2 vCPUs
>> 8 GB of disk
>> 1 GB of RAM (changing to 2 GB solves the problem)
>> Debian 9.3
>> ---
>>  README.md | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/README.md b/README.md
>> index f68bee5..d08a10c 100644
>> --- a/README.md
>> +++ b/README.md
>> @@ -23,6 +23,8 @@ https://github.com/cloudius-systems/osv/wiki
>>  OSv can only be built on a 64-bit x86 Linux distribution. Please note
>> that
>>  this means the "x86_64" or "amd64" version, not the 32-bit "i386"
>> version.
>>
>> +Compilation requires at least 2GB of RAM.
>> +
>>  If you wish, you can run the script 'scripts/setup.py' as root to install
>> all dependencies.
>>  Otherwise, you may follow the manual instructions below.
>>
>> @@ -39,8 +41,6 @@ Debian stable(wheezy) requires to compile gcc, gdb and
>> qemu.
>>  And also need to configure bridge manually.
>>
>>  More details are available on wiki page:
>> -[Building OSv on Debian stable][]
>> -
>>  [Building OSv on Debian stable]:
>> https://github.com/cloudius-systems/osv/wiki/Building-OSv-on-Debian-stable
>>
>>  **Debian testing(jessie)**
>> --
>> 2.7.4
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "OSv Development" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to osv-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[PATCH] Makefile: strip dummy-shlib.so

[geraldo netto]

with this small change we reduce dummy-shlib.so size from 8.24 KB to 5.62 KB
i have tested the build with tomcat and some other apps, everything looks good

Signed-off-by: geraldo netto 
---
 Makefile | 37 +++--
 1 file changed, 19 insertions(+), 18 deletions(-)

diff --git a/Makefile b/Makefile
index 8dd2371..80a1137 100644
--- a/Makefile
+++ b/Makefile
@@ -410,6 +410,7 @@ cmdline = --nomount tests/tst-hello.so
 endif
 
 $(out)/loader-stripped.elf: $(out)/loader.elf
+   $(call quiet, $(STRIP) $(out)/dummy-shlib.so, STRIP dummy-shlib.so )
$(call quiet, $(STRIP) $(out)/loader.elf -o $(out)/loader-stripped.elf, 
STRIP loader.elf -> loader-stripped.elf )
 
 ifeq ($(arch),x64)
@@ -554,23 +555,23 @@ bsd += bsd/porting/mmu.o
 bsd += bsd/porting/pcpu.o
 bsd += bsd/porting/bus_dma.o
 bsd += bsd/porting/kobj.o
-bsd += bsd/sys/netinet/if_ether.o  
-bsd += bsd/sys/compat/linux/linux_socket.o  
-bsd += bsd/sys/compat/linux/linux_ioctl.o  
-bsd += bsd/sys/net/if_ethersubr.o  
-bsd += bsd/sys/net/if_llatbl.o  
-bsd += bsd/sys/net/radix.o  
-bsd += bsd/sys/net/route.o  
-bsd += bsd/sys/net/raw_cb.o  
-bsd += bsd/sys/net/raw_usrreq.o  
-bsd += bsd/sys/net/rtsock.o  
-bsd += bsd/sys/net/netisr.o  
-bsd += bsd/sys/net/netisr1.o  
-bsd += bsd/sys/net/if_dead.o  
-bsd += bsd/sys/net/if_clone.o  
-bsd += bsd/sys/net/if_loop.o  
-bsd += bsd/sys/net/if.o  
-bsd += bsd/sys/net/pfil.o  
+bsd += bsd/sys/netinet/if_ether.o
+bsd += bsd/sys/compat/linux/linux_socket.o
+bsd += bsd/sys/compat/linux/linux_ioctl.o
+bsd += bsd/sys/net/if_ethersubr.o
+bsd += bsd/sys/net/if_llatbl.o
+bsd += bsd/sys/net/radix.o
+bsd += bsd/sys/net/route.o
+bsd += bsd/sys/net/raw_cb.o
+bsd += bsd/sys/net/raw_usrreq.o
+bsd += bsd/sys/net/rtsock.o
+bsd += bsd/sys/net/netisr.o
+bsd += bsd/sys/net/netisr1.o
+bsd += bsd/sys/net/if_dead.o
+bsd += bsd/sys/net/if_clone.o
+bsd += bsd/sys/net/if_loop.o
+bsd += bsd/sys/net/if.o
+bsd += bsd/sys/net/pfil.o
 bsd += bsd/sys/net/routecache.o
 bsd += bsd/sys/netinet/in.o
 bsd += bsd/sys/netinet/in_pcb.o
@@ -1947,7 +1948,7 @@ libuutil-objects = $(foreach file, $(libuutil-file-list), 
$(out)/bsd/cddl/contri
 
 define libuutil-includes
   bsd/cddl/contrib/opensolaris/lib/libuutil/common
-  bsd/cddl/compat/opensolaris/include 
+  bsd/cddl/compat/opensolaris/include
   bsd/sys/cddl/contrib/opensolaris/uts/common
   bsd/sys/cddl/compat/opensolaris
   bsd/cddl/contrib/opensolaris/head
-- 
2.7.4

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[COMMIT osv-apps master] apps/rogue: fix compilation

[Commit Bot]

From: Nadav Har'El 
Committer: Nadav Har'El 
Branch: master

apps/rogue: fix compilation

The rogue application compiles ncurses 5.9, but incorrectly used
header files from the system. If those are too new, rogue cannot
compile. So fix the Makefile to use the header files we downloaded
from ncurses 5.9.

Also use the opportunity to go back to downloading rogue from
rogueforge.net, which is back online, instead of a mirror.

Signed-off-by: Nadav Har'El 

---
diff --git a/rogue/GET b/rogue/GET
--- a/rogue/GET
+++ b/rogue/GET
@@ -23,13 +23,13 @@ make
 cd ..

 # Get and compile Rogue
-#wget http://rogue.rogueforge.net/files/rogue5.4/rogue5.4.4-src.tar.gz
-#tar zxvf rogue5.4.4-src.tar.gz
-#cd rogue5.4.4
-wget -c https://github.com/phs/rogue/archive/master.tar.gz
-tar zxvf master.tar.gz
-cd rogue-master
-CFLAGS="-fPIC -O2" ./configure --prefix=/usr
+wget http://rogue.rogueforge.net/files/rogue5.4/rogue5.4.4-src.tar.gz
+tar zxvf rogue5.4.4-src.tar.gz
+cd rogue5.4.4
+#wget -c https://github.com/phs/rogue/archive/master.tar.gz
+#tar zxvf master.tar.gz
+#cd rogue-master
+CFLAGS="-fPIC -O2 -I../ncurses-5.9/include" ./configure --prefix=/usr
 cat >> Makefile << END
 LDFLAGS=-pie
 LIBS=../ncurses-5.9/lib/libncurses.a
diff --git a/rogue/usr.manifest b/rogue/usr.manifest
--- a/rogue/usr.manifest
+++ b/rogue/usr.manifest
@@ -1,2 +1,2 @@
-/usr/games/rogue: ${MODULE_DIR}/upstream/rogue-master/rogue
+/usr/games/rogue: ${MODULE_DIR}/upstream/rogue5.4.4/rogue
 /usr/share/terminfo/u/unknown:  
${MODULE_DIR}/upstream/fixed-terminfo/u/unknown


--
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PATCH v2 1/2] manifest_common: avoid error when splitting paths

[Nadav Har'El]

On Fri, Feb 16, 2018 at 5:19 AM, geraldo netto 
wrote:

> Signed-off-by: geraldo netto 
> ---
>  scripts/manifest_common.py | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/scripts/manifest_common.py b/scripts/manifest_common.py
> index 58b0794..bfe5837 100644
> --- a/scripts/manifest_common.py
> +++ b/scripts/manifest_common.py
> @@ -52,10 +52,10 @@ def read_manifest(fn):
>  comment = re.compile("^[ \t]*(|#.*|\[manifest])$")
>  with open(fn, 'r') as f:
>  for line in f:
> -line = line.rstrip();
> +line = line.rstrip()
>  if comment.match(line): continue
> -components = line.split(": ", 2)
> -guestpath = components[0].strip();
> +components = line.split(":", 2)
>

While this used to be the case in the past, I wonder if it's a good idea.
It means we can never have a filename with a colon in it.
Wouldn't it make more sense to just fix the one or very few packages which
still have a colon without space, like I did in
commit dfdf08f6b9554af357e245992e0deadc6228d790?

I see a missing space in apps/ImageMagick/Makefile in one place. I couldn't
find any other such problem. If that's the only
one I think it's better to fix it.



+guestpath = components[0].strip()
>  hostpath = components[1].strip()
>  ret.append((guestpath, hostpath))
>  return ret
> --
> 2.7.4
>
> --
> You received this message because you are subscribed to the Google Groups
> "OSv Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to osv-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[COMMIT osv master] setup.py: add support for Debian 9.3 64-bits

[Commit Bot]

From: geraldo netto 
Committer: Nadav Har'El 
Branch: master

setup.py: add support for Debian 9.3 64-bits

Signed-off-by: geraldo netto 
Message-Id: <1519278021-5325-4-git-send-email-geraldone...@gmail.com>

---
diff --git a/scripts/setup.py b/scripts/setup.py
--- a/scripts/setup.py
+++ b/scripts/setup.py
@@ -165,41 +165,54 @@ class Debian(object):
 packages = [
 'ant',
 'autoconf',
+'automake',
+'bison',
 'build-essential',
+'curl',
+'flex',
 'gawk',
 'gdb',
 'genromfs',
+'git',
 'gnutls-bin',
-'lib32stdc++-4.9-dev',
 'libboost-all-dev',
 'libedit-dev',
 'libmaven-shade-plugin-java',
 'libncurses5-dev',
 'libssl-dev',
 'libtool',
+'libyaml-cpp-dev',
 'maven',
-'openjdk-7-jdk',
 'openssl',
 'p11-kit',
 'python-dpkt',
 'python-requests',
 'qemu-system-x86',
 'qemu-utils',
 'tcpdump',
+'unzip',
+'wget',
 ]

 ec2_packages = standard_ec2_packages
 test_packages = ['libssl-dev', 'zip']
 ec2_post_install = None

 class debian(object):
-packages = []
+packages = ['lib32stdc++-4.9-dev', 'openjdk-7-jdk',]
 ec2_packages = []
 test_packages = []
 ec2_post_install = None
 version = 'jessie/sid'

-versions = [debian]
+class Debian_9_3(object):
+packages = ['lib32stdc++-6-dev', 'openjdk-8-jdk',]
+ec2_packages = []
+test_packages = []
+ec2_post_install = None
+version = '9.3'
+
+versions = [debian, Debian_9_3]

 class Ubuntu(object):
 name = 'Ubuntu'

--
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[COMMIT osv master] setup.py: add curl to fedora package list

[Commit Bot]

From: geraldo netto 
Committer: Nadav Har'El 
Branch: master

setup.py: add curl to fedora package list

Signed-off-by: geraldo netto 
Message-Id: <1519278021-5325-2-git-send-email-geraldone...@gmail.com>

---
diff --git a/scripts/setup.py b/scripts/setup.py
--- a/scripts/setup.py
+++ b/scripts/setup.py
@@ -29,6 +29,7 @@ class Fedora(object):
 'automake',
 'bison',
 'boost-static',
+'curl',
 'flex',
 'gcc-c++',
 'gcc-c++-aarch64-linux-gnu',

--
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PATCH v2 1/3] setup.py: add curl to fedora package list

[Nadav Har'El]

I'll commit this, as it can't hurt, but note that it won't help either -
curl is installed by default on every Fedora installation:

$ dnf groups info Core
Group: Core
 Description: Smallest possible installation
 Mandatory Packages:
 ...
 curl




--
Nadav Har'El
n...@scylladb.com

On Thu, Feb 22, 2018 at 7:40 AM, geraldo netto 
wrote:

> Signed-off-by: geraldo netto 
> ---
>  scripts/setup.py | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/scripts/setup.py b/scripts/setup.py
> index 6e3c197..265156a 100755
> --- a/scripts/setup.py
> +++ b/scripts/setup.py
> @@ -29,6 +29,7 @@ class Fedora(object):
>  'automake',
>  'bison',
>  'boost-static',
> +'curl',
>  'flex',
>  'gcc-c++',
>  'gcc-c++-aarch64-linux-gnu',
> --
> 2.7.4
>
> --
> You received this message because you are subscribed to the Google Groups
> "OSv Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to osv-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PATCH] explicitly tell at README.md that compilation requires at least 2GB of RAM

[Nadav Har'El]

On Thu, Feb 22, 2018 at 6:02 AM, geraldo netto 
wrote:

> this will avoid people having such situation below:
> ...
>   CXX core/commands.cc
> virtual memory exhausted: Cannot allocate memory
>

I'm not comfortable with saying just that "2 GB of memory is needed for the
compilation". What is this number based on? For example, it strongly
depends on how much compilation you do in parallel, e.g., if "make -j4"
doesn't work, because it compiles 4 source files in parllel, probably "make
-j1" would. What "-j" option did you try? Also the amount of memory you
need also depends on what else you have running on your machine - and
whether you have swap (I guess you had none).

Nobody would set up a physical host today with just 1 GB of memory. A local
shop here which I recently went to sells its most basic setups with 4 GB.
And if you set up a VM with just 1 GB of memory and no swap, isn't it
obvious that if you get errors like "virtual memory exhausted" you need to
increase your memory?

By the way, something which is more deterministic and perhaps more
surprising that memory usage is the build's disk usage. Users should have
at least 3 GB of free disk space, because of some surprising disk usage of
the git files (700 MB) and the "external" directory (1.2 GB).


> make: *** [build/release.x64/core/commands.o] Error 1
> Makefile:363: recipe for target 'build/release.x64/core/commands.o' failed
> make failed. Exiting from build script
>
> VM configuration:
> VMWare player
> 2 vCPUs
> 8 GB of disk
> 1 GB of RAM (changing to 2 GB solves the problem)
> Debian 9.3
> ---
>  README.md | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/README.md b/README.md
> index f68bee5..d08a10c 100644
> --- a/README.md
> +++ b/README.md
> @@ -23,6 +23,8 @@ https://github.com/cloudius-systems/osv/wiki
>  OSv can only be built on a 64-bit x86 Linux distribution. Please note that
>  this means the "x86_64" or "amd64" version, not the 32-bit "i386" version.
>
> +Compilation requires at least 2GB of RAM.
> +
>  If you wish, you can run the script 'scripts/setup.py' as root to install
> all dependencies.
>  Otherwise, you may follow the manual instructions below.
>
> @@ -39,8 +41,6 @@ Debian stable(wheezy) requires to compile gcc, gdb and
> qemu.
>  And also need to configure bridge manually.
>
>  More details are available on wiki page:
> -[Building OSv on Debian stable][]
> -
>  [Building OSv on Debian stable]: https://github.com/cloudius-
> systems/osv/wiki/Building-OSv-on-Debian-stable
>
>  **Debian testing(jessie)**
> --
> 2.7.4
>
> --
> You received this message because you are subscribed to the Google Groups
> "OSv Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to osv-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.