Hello,
Jan-Benedict Glaw from the GCC project runs a Buildbot which tests the targets
mentioned in "contrib/config-list.mk" of the GCC sources.
http://gcc.gnu.org/ml/gcc/2013-11/msg00492.html
This could be very helpful for RTEMS since RTEMS GCC configurations regularly
break due to general GCC development.
Most RTEMS targets are listed in "contrib/config-list.mk". The PowerPC target
is a bit odd "powerpc-rtems4.11OPT-enable-threads=yes". Firstly it has version
in its name. Secondly its the only RTEMS target which uses the
"-enable-threads=yes" option.
The --enable-threads GCC configure option can be controlled via
"gcc/config.gcc":
*-*-rtems*)
case ${enable_threads} in
yes) thread_file='rtems' ;;
esac
Does it make sense to build RTEMS without the RTEMS thread model enabled? The
RSB and the RPM build infrastructure always uses the "--enable-threads" option.
Why don't we make this to the default?
*-*-rtems*)
case ${enable_threads} in
no)
;;
"" | yes | rtems)
thread_file='rtems'
;;
*)
echo 'Unknown thread configuration for RTEMS'
exit 1
;;
esac
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel
