From: W.P. <laurentp@wp.pl>
To: buildroot@busybox.net
Subject: [Buildroot] setting up buildroot for using OLD gcc / binutils
Date: Fri, 16 Oct 2009 19:37:52 +0200 [thread overview]
Message-ID: <4AD8AF70.9050506@wp.pl> (raw)
In-Reply-To: <4AD63754.5020502@arcor.de>
U?ytkownik Sebastian napisa?:
> Hello,
>
>>> You can always use an older version of buildroot.
>>> [...]
>>>
>> Sorry, don't understand. I need to make cross-compile environement with
>> following "parameters":
>>
>> gcc: 3.4.4
>> binutils 2.15.94
>> kernel 2.6.12.6-venus
>> uClibc 0.9.28
>> busybox 1.1.3
>>
>> and i am trying to do this with buildroot. could you help?
>
> Do the following:
>
> $ git clone git://git.buildroot.net/buildroot
> $ cd buildroot/
> $ git reset --hard gcc3_legacy
> $ make menuconfig
>
> Make sure to activate
> "Build options" --> "Show packages that are deprecated or obsolete"
>
> Now you have a version which allows you to use:
>
> gcc 3.4.4
> binutils 2.15 or 2.15.94.0.2.2
> kernel 2.6.12
> uClibc 0.9.28
> busybox 1.1.3
>
> You probably can't get closer to your wished versions (easily).
>
> I don't know what your "-venus" kernel means, but if you want to build
> a kernel module without the _exact_ sources you will probably be out
> of luck.
>
> Make sure you tell us if it works! :-)
>
> I do not know how to operate git, and I could not find any reference
> to the old SVN repository (if it still exists...), so you may be
> better off asking someone else.
>
> I hope I could help,
Great thanks, at least things started to build.
But I got uClibc bigger than on real system. This may be because of
options selected by default. (at least what is WRONG in uClibc.config is
TARGET_ARCH=none, KERNEL_SOURCE=/usr/src/linux,
KERNEL_HEADERS=/usr/src/linux/include -> this points to my i386 kernel
files).
So my question for now is how do I selectively "make clean uClibc"? As I
want to "play" with uClibc options.
And second one: how to prevent "make clean" from erasing downloads?
W.P.
prev parent reply other threads:[~2009-10-16 17:37 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
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. [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=4AD8AF70.9050506@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.