[ Add AG for the moxie issue ]
On 9/10/2014 8:31 am, Joel Sherrill wrote:
On 10/5/2014 1:23 AM, Chris Johns wrote:
Hi,
There are a few issues with 4.9.1 which need to be looked at. I have not
attempted a Windows build yet.
My question is:
Do we move the architectures that *do* build to 4.9.1 ?
I would lean to yes or wait for 4.9.2 to be released since it should be
close.
I will move the ones we know build. Newlib is now at the very latest via
git.
m32c:
configure: error: unable to detect exception model
Is this trying C++?
No ...
http://git.rtems.org/rtems-source-builder/tree/rtems/config/4.11/rtems-m32c.bset#n14
It is building libgcc which wants to know the exception model for some
reason. I do not know if there is a configure option to handle this or
something in our target support that is different.
m32c does not support C++ at all. End of story.
Understood.
moxie:
We are using binutils-2.24. Is there a later release ?
CC_TLS -DUSE_EMUTLS -o _gcov.o -MT _gcov.o -MD -MP -MF _gcov.dep
-DL_gcov -c ../../../../gcc-4.9.1/libgcc/libgcov-driver.c
/tmp//cc7Lxv5S.s: Assembler messages:
/tmp//cc7Lxv5S.s:176: Error: unknown opcode sex.b $r0,$r0
[ AG, a rather interesting name for an instruction ]
Anthony, any ideas here ?
Chris
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
