From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] [ARM] Status for last 13 unclean-building ARM boards
Date: Wed, 21 Sep 2011 07:32:41 +0200 [thread overview]
Message-ID: <4E7976F9.50002@aribaud.net> (raw)
In-Reply-To: <4E791A86.9020100@discworld.dascon.de>
Le 21/09/2011 00:58, Michael Schwingen a ?crit :
> Am 09/20/2011 10:44 PM, schrieb Albert ARIBAUD:
>> Just tried actux3 - I get only this one warning:
>>>
>>> /usr/local/pkg/x-tools/armeb-unknown-linux-gnu/bin/.armeb-unknown-linux-gnu-ld:
>>>
>>> warning: creating a DT_TEXTREL in object.
>>>
>>> AFAIK, that one has been there since relocation was added.
>>>
>>> I compile using
>>>> export
>>> CROSS_COMPILE=/opt/x-tools/armeb-unknown-linux-gnu/bin/armeb-unknown-linux-gnu-
>>>
>>>> make
>>>
>>> /opt/x-tools/armeb-unknown-linux-gnu/bin/armeb-unknown-linux-gnu-gcc -v
>>
>> Microcross X tools -- no free version apparently...
>>
>>> gcc version 4.3.4 (crosstool-NG-hg_default at 1471_4a88cb9bfe8f)
>>
>> ... but it seems like it is a standard crosstool ng build. Guess I'll
>> have to build my own if I want to be able to .MAKEALL these boards...
>> Thanks for the info.
> Um - no. These compilers were built from scratch using crosstools-ng - I
> am not sure where the x-tools directory name came from, but this is
> definitely a local build from free sources, not some closed binary.
Thanks for the clarification. I was indeed misled by the 'x-tools' name.
> cu
> Michael
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-09-21 5:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 8:12 [U-Boot] [STATUS] [ARM] Status for last 13 unclean-building ARM boards Albert ARIBAUD
2011-09-19 6:15 ` Stefan Roese
2011-09-19 18:40 ` Michael Schwingen
2011-09-20 20:44 ` Albert ARIBAUD
2011-09-20 22:58 ` Michael Schwingen
2011-09-21 5:32 ` Albert ARIBAUD [this message]
2011-09-21 5:51 ` Stefan Roese
2011-09-22 11:56 ` Dirk Behme
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=4E7976F9.50002@aribaud.net \
--to=albert.u.boot@aribaud.net \
--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 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.