joel.sherrill at OARcorp.com
Sun Nov 8 23:37:31 UTC 2009
Ralf Corsepius wrote:
> On 11/06/2009 06:43 PM, Leontie Eugen wrote:
>> Sorry for being vague. I am doing a RTEMS port to sparc64,
> Wow, a 64bit target ... the "beyond bleeding edge"!
> FWIW: I am not aware about anybody having successfully ported RTEMS to a
> 64bit target before, nor am I sure if RTEMS is "64bit ready".
> (I know, RTEMS is not 16bit clean, but I am working on this)
The mips port includes a 64-bit variant. I never heard any complaints.
Worst case, the target will get warnings or errors and we will work
together to fix them.
>> so I have a new processor model, new bsp and the rtems is the latest CVS from a couple weeks back.
> Upgrade to the very latest CVS-HEAD. A lot of "bit-wise" cleanup has
> gone into CVS-HEAD recently (and more will likely follow).
>> I found this conversation online : http://old.nabble.com/-patch,rtems--Don't-build-__assert_func-for-RTEMS-td25554127.html
>> and it is exactly what I need. Can you explain how should I configure NEWLIB for that, or how would I activate HAVE___ASSERT_FUNC ?
> Try the very latest newlib*rtems4.10*.diff from
> contrib/crossrpms/patches in rtems CVS-HEAD and rebuild your GCC/newlib
> one-tree style with it.
> It contains the very latest adaptation of the patch to the RTEMS-4.10
> toolchains you mention above.
> rtems-users mailing list
> rtems-users at rtems.org
More information about the users