From: W.P. <laurentp@wp.pl>
To: buildroot@busybox.net
Subject: [Buildroot] setting up buildroot for using OLD gcc / binutils
Date: Wed, 14 Oct 2009 00:13:36 +0200 [thread overview]
Message-ID: <4AD4FB90.2060202@wp.pl> (raw)
In-Reply-To: <4AD4E640.2030103@arcor.de>
U?ytkownik Gammalsvenska napisa?:
>>> No, I didn't. But for binutils 2.15.94.0.2.2 patch directory is
>>> empty in
>>> 2009-02, and there are patches in 0.9.27 in 2.15.94.0.2 dir.
>>>
>>> Will try and report results.
>>>
>> Made "patches" for Config.in for kernel headers, gcc and binutils. No
>> software packages/kernel selected, just toolchain.
>>
>> First error (download generic 2.6.12.6 kernel OK, and then error):
> > [...]
>> `/usr/src/buildroot/toolchain_build_mipsel/linux-2.6.12.6'
>> Makefile:485: .config: No such file or directory
>> make[1]: *** No rule to make target `headers_install'. Stop.
>> make[1]: Leaving directory
>> `/usr/src/buildroot/toolchain_build_mipsel/linux-2.6.12.6'
>> make: *** [/usr/src/buildroot/toolchain_build_mipsel/linux/.configured]
>> Error 2
>> [root at laurent-home buildroot]#
>>
>> What should I do?
>
>
> You can always use an older version of buildroot.
> There are no releases earlier than 2009.05, but it was maintained back
> then. Snapshots were done in subversion (nowadays they use git) and
> you can always use an older version from there.
>
> Try to find out which releases are appropriate for you. Manually
> patching is probably not working too well as in recent releases old
> versions have been removed including workarounds needed.
>
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?
W.P.
> Best regards,
> Sebastian
next prev parent reply other threads:[~2009-10-13 22:13 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. [this message]
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=4AD4FB90.2060202@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox