From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] setting up buildroot for using OLD gcc / binutils
Date: Tue, 13 Oct 2009 13:10:09 +0200 [thread overview]
Message-ID: <20091013111009.GB23718@mx.loc> (raw)
In-Reply-To: <4AD3B2BE.2010809@wp.pl>
On Tue, Oct 13, 2009 at 12:50:38AM +0200, W.P. wrote:
>There is a system (Manta "Multimedia Recorder" HDD-2000 = Shenzen Mele
>HMC-35HD) that was build using (i am almost sure after several hours of
>googling) using those versions of tools. And binutils: 2.16 or even
>2.15. I want to be able to build some kernel modules, so (correct me if
>I am wrong) I need EXACT versions of tools/configure options to do so.
for kernel modules it's a 80%-90% yes.
>
>BTW It looks crazy, those Chinese/Taiwanese developpers (Mele, Edimax,
>maybe others) seems to be TIED to gcc 3.4.4(3).....
It is. It's a pity that this way eventual (size)regressions don't get
fixed. I'f nevertheless try to build the module with 3.4.6 and see if
that works.
>(look at published Edimax toolchains for BR-6204Wg, BR-6104KP...)
>
>BTW2: looks Manta(Poland) violates GPL.... : there is NO mention about
>sources on their web.
I think there is a paragraph on the busybox page:
http://busybox.net/license.html#enforce
next prev parent reply other threads:[~2009-10-13 11:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 19:55 [Buildroot] setting up buildroot for using OLD gcc / binutils W.P.
2009-10-12 20:04 ` Peter Korsgaard
2009-10-12 20:28 ` W.P.
[not found] ` <20091012203645.GX2266@mx.loc>
2009-10-12 22:50 ` W.P.
2009-10-13 11:10 ` Bernhard Reutner-Fischer [this message]
2009-10-13 18:06 ` W.P.
2009-10-13 18:17 ` Peter Korsgaard
2009-10-13 18:32 ` W.P.
2009-10-13 19:41 ` W.P.
[not found] ` <4AD4E640.2030103@arcor.de>
2009-10-13 22:13 ` W.P.
2009-10-14 20:40 ` Sebastian
2009-10-16 17:37 ` W.P.
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=20091013111009.GB23718@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.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