From: "Alex" <halo2@aon.at>
To: <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Building
Date: Sun, 16 Dec 2012 00:00:01 +0100 (CET) [thread overview]
Message-ID: <131.130.222.214.1355612401.wm@webmail.inode.at> (raw)
Hi!
Thanks for the nice project.
Building like described at
http://www.bufferbloat.net/projects/cerowrt/wiki/Building_Cerowrt_on_your_own_machine
at least needs the diff added as attachment
and a
scripts/feeds install libgpgme
(for opkg-gpg)
so then a make menuconfig
left then are undefined symbol
PACKAGE_pptp
PACKAGE_libcrypto
still have to fix that
pptp got ppp-mod-pptp and so its only luci-proto-ppp
libcrypto is in libopenssl
and also a kernel_menuconfig
I think many of this things will be fixed in your environments? Or are
they just old.
Would be good for people who want to try it fast to apply my provided
patch and propably an better config and kernel config?
By the way, what brought me there is I'm searching for an easy way to geht
the relevant buffer/queue changes into openwrt, as building this big
release customized for one platform doesn't seem efficient to me for
deploying and testing.
Customized IP's, passwords dont make it easier too.
So can you propably give little help on where the patchset I seek could be?
It's an interesting topic and I like to test it.
On my 2048/512 Kbit DSL only a few things seem to work as they should (yea
got an wndr3800 for that), so using VMs and x86 seems a better approach
for simulating by now.
Ah, okay, just found http://snapon.lab.bufferbloat.net/~cero2/cerowrt/3.6/.
Even x86 there as vmdk, very nice.
Why dont post these links on the sites, and also for the build environment
or so?
Thanks
Alex
next reply other threads:[~2012-12-15 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 23:00 Alex [this message]
2012-12-19 16:17 ` Dave Taht
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=131.130.222.214.1355612401.wm@webmail.inode.at \
--to=halo2@aon.at \
--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