From: Maciej Soltysiak <maciej@soltysiak.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] How much disk space is required to build cero?
Date: Wed, 16 Jul 2014 13:42:49 +0200 [thread overview]
Message-ID: <CAMZR1YAUGUS4zE0m9NRsZHpx1C3EP+5ubO-Fagqs5Wz6yfOKow@mail.gmail.com> (raw)
Hi list!
Can anyone tell me, roughly, how much disk space is required to build
cero nowadays? I understand the instructions [1] are still valid.
I wanted to experiment on builds but always ran out of disk space and
never could provide tested patches.
This time I want to try an upgrade to dnscrypt to 1.4.0 and the
depending libsodium library from 0.4.5 to 0.6.1 so that I can test if
it works with the --enable-minimal switch for embedded systems, which
should produce smaller .so size.
Best regards,
Maciej
[1] http://www.bufferbloat.net/projects/cerowrt/wiki/Building_Cerowrt_on_your_own_machine
next reply other threads:[~2014-07-16 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 11:42 Maciej Soltysiak [this message]
2014-07-16 12:44 ` Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMZR1YAUGUS4zE0m9NRsZHpx1C3EP+5ubO-Fagqs5Wz6yfOKow@mail.gmail.com \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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