I guess this just follows the pattern used for binutils/gdb on same targets. Seems fine to me.
On Fri, Jul 20, 2018 at 4:53 AM, Sebastian Huber <sebastian.hu...@embedded-brains.de> wrote: > --- > source-builder/config/gcc-common-1.cfg | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/source-builder/config/gcc-common-1.cfg > b/source-builder/config/gcc-common-1.cfg > index 03d84bc..b432fdf 100644 > --- a/source-builder/config/gcc-common-1.cfg > +++ b/source-builder/config/gcc-common-1.cfg > @@ -66,8 +66,8 @@ BuildRoot: %{_tmppath}/%{name}-root-%(%{__id_u} -n) > cd ${build_top} > > # newlib > - source_dir_newlib="newlib-%{newlib_version}" > - %source setup newlib -q -D -n newlib-%{newlib_version} > + > source_dir_newlib=%{?newlib_external:%{newlib_expand_name}}%{!?newlib_external:"newlib-%{newlib_version}"} > + %source setup newlib -q -D -n ${source_dir_newlib} > %patch setup newlib -p1 > cd ${build_top} > > -- > 2.13.7 > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel