From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Pointers on build setup?
Date: Tue, 1 May 2012 01:32:25 +0200 [thread overview]
Message-ID: <CAMZR1YB6Y6wW+Xn+CcwfBGxnEyjxNKmnk3WJVZtevJqMtEZCtg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4bqvE6vGhw5rAOhP64A=Vwp-XDJ0UgDfbj9_0GQbW3mQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]
Hi Dave,
I'm following the cleaned up "Building_Cerowrt_on_your_own_machine" and I
only edited one line that wasn't right about cd'ing into a directory.
It's compiling now, will leave it for the night.
However, can you tell me, how far away will I be from the builds that you
are putting up for download if I stick to the instruction and not change a
single .config entry or add/change/remove a package?
Regards,
Maciej
On Mon, Apr 30, 2012 at 6:50 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Mon, Apr 30, 2012 at 8:50 AM, Dave Taht <dave.taht@gmail.com> wrote:
> > On Mon, Apr 30, 2012 at 8:14 AM, <dpreed@reed.com> wrote:
> >> Regarding builds - can someone who is building cerowrt from source
> >> (including kernel) point me at the recipe for building it completely
> from
> >> scratch?
>
> I have cleaned up build_cero.sh and corrected
>
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/Building_Cerowrt_on_your_own_machine
>
> As noted elsewhere I have not pushed out the last weeks worth of changes
> yet.
> (if you merge from openwrt head, things will break)
>
> In the long run there will be a packages-3.3 on a github repo, for
> stability.
>
>
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://www.bufferbloat.net
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2361 bytes --]
next prev parent reply other threads:[~2012-04-30 23:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 0:15 [Cerowrt-devel] speeding up builds Dave Taht
2012-04-30 1:42 ` Outback Dingo
2012-04-30 1:59 ` Dave Taht
2012-04-30 2:24 ` Dave Taht
2012-04-30 2:42 ` Dave Taht
2012-04-30 2:52 ` Dave Taht
2012-04-30 15:14 ` [Cerowrt-devel] Pointers on build setup? dpreed
2012-04-30 15:50 ` Dave Taht
2012-04-30 16:50 ` Dave Taht
2012-04-30 23:32 ` Maciej Soltysiak [this message]
2012-04-30 23:46 ` Dave Taht
2012-04-30 19:15 ` dpreed
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=CAMZR1YB6Y6wW+Xn+CcwfBGxnEyjxNKmnk3WJVZtevJqMtEZCtg@mail.gmail.com \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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