From: Gary Thomas <gary@mlbassoc.com>
To: Syed Ismail <ismail.riyaz@dyansys.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Redboot building issue
Date: Fri, 26 Oct 2007 09:34:00 -0000 [thread overview]
Message-ID: <4721B48E.5080604@mlbassoc.com> (raw)
In-Reply-To: <20071026075643.65218.qmail@pro3.rediffmailpro.com>
Syed Ismail wrote:
>
>
> On Thu, 25 Oct 2007 Gary Thomas wrote :
>> Syed Ismail wrote:
>>> Hi
>>> I am trying to build redboot for freescale based
>> mx31 ads platform.
>>> I am able to build it using arm-elf toolchain
>> provided by ecos. I havent
>>> tested it as yet for fear of crashing. I would like
>> to know if it is
>>> necessary to build it using the toolchain provided by
>> freescale only
>>> (this doesnt build).
>> Yes, this should work just fine.
>>
>> Which tools from FreeScale are you using? Why/how does
>> it fail?
>>
> Thanks for the followup. The tool from freescale is in
> /opt/freescale/usr/local/gcc-4.1.1-glibc-2.4-nptl-6/arm-none-linux-gnueabi/bin
> The tools in this directory are
> arm-none-linux-gnueabi-addr2line arm-none-linux-gnueabi-gcc arm-none-linux-gnueabi-objdump
> arm-none-linux-gnueabi-ar arm-none-linux-gnueabi-gcc-4.1.1 arm-none-linux-gnueabi-ranlib
> arm-none-linux-gnueabi-as arm-none-linux-gnueabi-gccbug arm-none-linux-gnueabi-readelf
> arm-none-linux-gnueabi-c++ arm-none-linux-gnueabi-gcov arm-none-linux-gnueabi-size
> arm-none-linux-gnueabi-c++filt arm-none-linux-gnueabi-ld arm-none-linux-gnueabi-strings
> arm-none-linux-gnueabi-cpp arm-none-linux-gnueabi-nm arm-none-linux-gnueabi-strip
> arm-none-linux-gnueabi-g++ arm-none-linux-gnueabi-objcopy fix-embedded-paths
> The error during build was arm-elf command not found.
> I changed it to arm-none-linux-gnueabi in the global build options.
> The error now is
> /home/ismail/src/ecos/packages/infra/current/src/diag.cxx:90: error: 'init_priority' attribute is not supported on this platform
> I am pretty new to ecos. So kindly explain as you would to such a one
> Thanks in advance
>
Please keep your replies on the mailing list so that all may benefit.
eCos [probably] won't work if you compile using those tools - you are
better off with the arm-elf tools that you used.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next parent reply other threads:[~2007-10-26 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071026075643.65218.qmail@pro3.rediffmailpro.com>
2007-10-26 9:34 ` Gary Thomas [this message]
2007-10-25 5:16 Syed Ismail
2007-10-25 11:24 ` Gary Thomas
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=4721B48E.5080604@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=ismail.riyaz@dyansys.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).