Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] libmusl woes
Date: Wed, 17 Jun 2015 09:59:32 -0700	[thread overview]
Message-ID: <CAA93jw5=Ru8a1VM5K=nQj9e3i6U3aNwdpaLdQ_+YSn3Lw2rHWQ@mail.gmail.com> (raw)
In-Reply-To: <878ubiimji.fsf@alrua-desktop.borgediget.toke.dk>

On Wed, Jun 17, 2015 at 4:47 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Dave Taht <dave.taht@gmail.com> writes:
>
>> I am not sure how (or even if I should) to switch back to uclibc,

The bigger question is: is openwrt's future direction musl? I don't
mind switching, but would prefer to switch in the right direction.


> Advanced configuration options (for developers) -> Toolchain Options ->
> C library implementation. Trunk builds fine with uClibc as far as I can
> tell...

make dirclean helped clean up the mess. Going to try both uclibc and
musl build again. (really did want to "see" what an linksys 1900ac
did... did not anticipate it being so hard)


>
> Tried fixing tinc, but it appears to be a clash within the header files
> with no solution forthcoming. See
> http://www.openwall.com/lists/musl/2012/10/11/4
>
> This script seems to fix it by modifying the Linux headers, but figure
> that is not feasible for an openwrt package recipe...
> https://github.com/lancethepants/tinc-arm-musl-static/blob/master/tinc.sh#L148
>
> -Toke



-- 
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast

  reply	other threads:[~2015-06-17 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17  6:05 Dave Taht
2015-06-17 11:47 ` Toke Høiland-Jørgensen
2015-06-17 16:59   ` Dave Taht [this message]
2015-06-19 19:13 ` 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='CAA93jw5=Ru8a1VM5K=nQj9e3i6U3aNwdpaLdQ_+YSn3Lw2rHWQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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