All of lore.kernel.org
 help / color / mirror / Atom feed
From: W.P. <laurentp@wp.pl>
To: buildroot@busybox.net
Subject: [Buildroot] setting up buildroot for using OLD gcc / binutils
Date: Tue, 13 Oct 2009 00:50:38 +0200	[thread overview]
Message-ID: <4AD3B2BE.2010809@wp.pl> (raw)
In-Reply-To: <20091012203645.GX2266@mx.loc>

U?ytkownik Bernhard Reutner-Fischer napisa?:
> On Mon, Oct 12, 2009 at 10:28:59PM +0200, W.P. wrote:
>   
>> U?ytkownik Peter Korsgaard napisa?:
>>     
>>>>>>>> "W" == W P <laurentp@wp.pl> writes:
>>>>>>>>             
>>>>>>>>                 
>>>  W> Hi,
>>>  W> how can I set up CURRENT buildroot to use OLD gcc/binutils/kernel/uClibc?
>>>  W> I need gcc 3.4.4, kernel 2.6.12.6-venus, uClibc 0.9.28?
>>>
>>> Some older toolchain versions are available if you enable BR_DEPRECATED
>>> (Build options->Show packages that are deprecated or obsolete). It won't
>>> give you those exact options, but it might be close enough.
>>>
>>>   
>>>       
>> Almost :(
>>
>> With choosing this option I am able to select gcc down-to 3.4.6,
>> binutils 2.17, uClibc 0.9.28.3, kernel 2.6.2x ...
>>
>> Could you point me to the file where are these choices are in? If I know
>> in what file, then adding an option ex. to gcc 3.4.4 instead of 3.4.6
>> should be easy...
>>     
>
> not really since you have to patch it.
> See toolchain/gcc/Config.in
>
> I'm curious why you think you need a compiler that is so full of
> bugs compared to let's say the current 4.x series?
>   

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.

BTW It looks crazy, those Chinese/Taiwanese developpers (Mele, Edimax,
maybe others) seems to be TIED to gcc 3.4.4(3).....
(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.

W.P.

  parent reply	other threads:[~2009-10-12 22:50 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. [this message]
2009-10-13 11:10         ` Bernhard Reutner-Fischer
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=4AD3B2BE.2010809@wp.pl \
    --to=laurentp@wp.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.