From: R Sricharan <r.sricharan@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ELDK4.2 build failures for highbank, omap4_panda and omap4_sdp4430
Date: Tue, 9 Oct 2012 11:16:06 +0530 [thread overview]
Message-ID: <5073BA1E.4020107@ti.com> (raw)
In-Reply-To: <20121008163516.GB6947@bill-the-cat>
On Monday 08 October 2012 10:05 PM, Tom Rini wrote:
> On Sat, Oct 6, 2012 at 4:34 AM, Albert ARIBAUD <albert.u.boot@aribaud.net> wrote:
>> Hi,
>>
>> On Sat, 6 Oct 2012 13:02:49 +0200, Albert ARIBAUD
>> <albert.u.boot@aribaud.net> wrote:
>>
>>> Hi All,
>>>
>>> With Anatolij's fix in, ELDK4.2 still fails to build three boards:
>>> highbank, omap4_panda and omap4_sdp4430 (maintainers CCed).
>>>
>>> Build logs are weird for the two omap boards:
>>>
>>> Configuring for omap4_panda board...
>>> arm-linux-gnueabi-size: './u-boot': No such file
>>> make: *** [checkthumb] Erreur 1
>>> make: INTERNAL: Exiting with 10 jobserver tokens available; should be 9!
>>> Configuring for omap4_sdp4430 board...
>>> arm-linux-gnueabi-size: './u-boot': No such file
>>> make: *** [checkthumb] Erreur 1
>>> make: INTERNAL: Exiting with 10 jobserver tokens available; should be 9!
>>>
>>> For highbank, it is a matter of emitting instructions invalid for
>>> armv5.
>>>
>>> Do these boards need to support building with older toolchains?
>>>
>>> Amicalement,
>>
>> Seems like sricharan at ti.com does not exist any more. That makes
>>
>> omap4_panda ARM ARMV7 (OMAP4xx SoC)
>> omap4_sdp4430 ARM ARMV7 (OMAP4xx SoC)
>> omap5_evm ARM ARMV7 (OMAP5xx Soc)
>>
>> Up for bids for a new maintainer.
>
> But that's not quite his email address :) Cc'ing him now but as I said later in the thread, it's a feature that it doesn't build for eldk4.2
>
Thats right. They are currently build with THUMB mode.
Regards,
Sricharan
next prev parent reply other threads:[~2012-10-09 5:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 9:31 [U-Boot] [PATCH] yaffs2: Fix GCC 4.6 compile warnings Anatolij Gustschin
2012-10-06 11:02 ` [U-Boot] ELDK4.2 build failures for highbank, omap4_panda and omap4_sdp4430 (was: [PATCH] yaffs2: Fix GCC 4.6 compile warnings) Albert ARIBAUD
2012-10-06 11:34 ` Albert ARIBAUD
2012-10-08 16:35 ` Tom Rini
2012-10-09 5:46 ` R Sricharan [this message]
2012-10-09 16:59 ` [U-Boot] ELDK4.2 build failures for highbank, omap4_panda and omap4_sdp4430 Albert ARIBAUD
2012-10-07 18:22 ` [U-Boot] ELDK4.2 build failures for highbank, omap4_panda and omap4_sdp4430 (was: [PATCH] yaffs2: Fix GCC 4.6 compile warnings) Tom Rini
2012-10-06 16:59 ` [U-Boot] [PATCH] yaffs2: Fix GCC 4.6 compile warnings Albert ARIBAUD
2012-10-09 18:09 ` Scott Wood
2012-10-09 18:51 ` Tom Rini
2012-10-09 19:08 ` Scott Wood
2012-10-09 21:53 ` Tom Rini
2012-10-08 18:47 ` [U-Boot] " Tom Rini
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=5073BA1E.4020107@ti.com \
--to=r.sricharan@ti.com \
--cc=u-boot@lists.denx.de \
/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