Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Oliver Niesner <oliver.niesner@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] always_stop_at_dbus_package
Date: Sat, 15 Sep 2012 17:37:30 -0700	[thread overview]
Message-ID: <CAA93jw5e1rfV+DLSXL0e=M8rW_aygWaJhpOVxtgWXp66uLXPBg@mail.gmail.com> (raw)
In-Reply-To: <5052E9F4.1090809@googlemail.com>

I currently build with 12.4.

I have been focused on matters other than code of late, but I would
certainly argue that 10.4 is rather ancient.

I can add aiccu to the build and thought I was building ipset as an
optional package.

That said, I think having a scrum/google hangout on getting more
people up to speed on "how to build openwrt and cerowrt" would be
helpful for many.


On Fri, Sep 14, 2012 at 1:25 AM, Oliver Niesner
<oliver.niesner@gmail.com> wrote:
> Hi, all!
>
> Sorry for bothering you again with those basic problems, but i need to get
> my own build working for
> the following reasons:
>
> 1) to get ipv6 working i need the package aiccu, as far as i know it's not
> in the current release of cerowrt
> 2) I use large filtering with ipset, but ipset (userspace+kernel module) is
> not in cerowrt by default
>
> Dave tried to help me, but unfortunately his hints doesn't work on my
> machine - i get always the dependency problem i posted before:
>
>> Package libdbus is missing dependencies for the following libraries:
>> libpthread.so.0
>> librt.so.0
>
>
> The make package/dbus/{clean,compile,install} V=99 and other things do not
> work for me :-/
> I do not use parallel builds with make -jx, as suggested.
>
> I use a special machine  (Core 2 Quad CPU    Q8300  @ 2.50GHz) for building
> with Ubuntu 10.04.4 LTS installed, maybe that is the main problem?
> What do you guys use for building cerowrt? Any hint would be useful.
> I really want to help out and provide everyone with useful info, if
> possible.
> I do not know too much about the openwrt/cerowrt buildsystem, but im willing
> to learn!
> If i get these problems solved it would be now problem too write my
> experiences down on the wiki to
> help others.
> Hope to get this fixed with your help.
>
> Thanks,
>
> Oliver
>
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
with fq_codel!"

  reply	other threads:[~2012-09-16  0:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  8:25 Oliver Niesner
2012-09-16  0:37 ` Dave Taht [this message]
2012-09-16  3:29   ` Mark Constable

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='CAA93jw5e1rfV+DLSXL0e=M8rW_aygWaJhpOVxtgWXp66uLXPBg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=oliver.niesner@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