From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot and Linux/ARM on AT91SAM9260
Date: Thu, 27 Dec 2007 14:42:59 +0200 [thread overview]
Message-ID: <47739DD3.8050400@promwad.com> (raw)
In-Reply-To: <4767A119.6070508@promwad.com>
>> I did finally get a build of the latest trunk of buildroot, but it had
>> a lot of problems. sshd and other non-busybox applications segfault.
>> This was using gcc 4.2.1, binutils 2.18 and a snapshot of uClibc from
>> early december, using softfloat and EABI. I've had to focus on some
>> other issues so I haven't gotten back to it yet. This was still with
>> my 2.6.21.6 kernel I'd built previously, still cannot get a working
>> 2.6.23 kernel with that toolchain.
>>
>
This commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1e621a8e3752367d4aae78a8ab00a18fb2793f34
fixes issue with build-id section introduced in 2.6.23
Hope you will finally have working 2.6.23 kernel.
Regards,
Ivan
--
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------
next prev parent reply other threads:[~2007-12-27 12:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 5:06 [Buildroot] make on MAC OS X Fan Zhang
2007-11-29 6:38 ` [Buildroot] uClibc-nptl? Ryan Ordway
2007-11-29 13:30 ` Steven J. Hill
2007-11-30 7:00 ` Ryan Ordway
2007-12-12 20:17 ` [Buildroot] Buildroot and Linux/ARM on AT91SAM9260 Ryan Ordway
2007-12-17 16:14 ` Ivan Kuten
2007-12-17 19:38 ` Ryan Ordway
2007-12-17 20:33 ` Ivan Kuten
2007-12-17 22:49 ` Ivan Kuten
2007-12-17 22:53 ` Ryan Ordway
2007-12-17 23:24 ` Ryan Ordway
2007-12-17 23:36 ` Ivan Kuten
2007-12-18 0:24 ` Ryan Ordway
2007-12-18 10:29 ` Ivan Kuten
2007-12-27 12:42 ` Ivan Kuten [this message]
2008-01-12 16:42 ` Wayne Keenan
2008-01-12 16:43 ` Wayne Keenan
2008-01-12 22:39 ` Wayne Keenan
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=47739DD3.8050400@promwad.com \
--to=ivan.kuten@promwad.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 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.