From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Who is the wrt54oe maintainer?
Date: Mon, 19 May 2008 14:04:11 +0200 [thread overview]
Message-ID: <g0rqbs$fa5$1@ger.gmane.org> (raw)
In-Reply-To: <200805191026.10545.openembedded@haerwu.biz>
Marcin Juszkiewicz wrote:
> Dnia niedziela, 18 maja 2008, Michael 'Mickey' Lauer napisał:
>> On Thursday 15 May 2008 00:05:25 Leon Woestenberg wrote:
>>> who is the wrt54oe distro maintainer?
>> Unfortunately, there's no one. I always had the hope we could get one
>> of the openwrt-fork-maintainers on board. Marcin and me once did some
>> work towards having this popular device in OE, but we both could not
>> find enough time to keep it up.
>
> wrt54 + wrt54oe was working combo to build packages for OpenWRT
> installation. Today we also have distro config to build such ones with
> OpenWRT provided toolchain.
>
>>> It needs love in conf/distro/wrt54oe.conf, as it isn't up to date
>>> with our external toolchain opt-in, binutils-cross is not locked
>>> down, and the c library was not chosen, nor its version.
>> Indeed. Could I talk you into adding the necessary bits?
>
> It should be uclibc 0.9.27 (or newer if binary compatible), binutils 2.18,
> gcc 3.4.4.
Note that "binary compatible" doesn't mean a lot when using uClibc. If
you change the defconfig within the same version you can get "binary
incompatible"[1] results on some or all depending applications.
regards,
Koen
[1] I'm not sure how that effects our site files for autotools.
prev parent reply other threads:[~2008-05-19 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 22:05 Who is the wrt54oe maintainer? Leon Woestenberg
2008-05-18 21:55 ` Michael 'Mickey' Lauer
2008-05-19 8:26 ` Marcin Juszkiewicz
2008-05-19 12:04 ` Koen Kooi [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='g0rqbs$fa5$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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