On 10/03/2015 2:05 am, Hesham ALMatary wrote:
On Mon, Mar 9, 2015 at 2:45 PM, Gedare Bloom <ged...@gwu.edu> wrote:
On Sun, Mar 8, 2015 at 5:46 PM, Chris Johns <chr...@rtems.org> wrote:
On 6/03/2015 1:23 am, Hesham ALMatary wrote:
---
rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg
b/rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg
index 297f4e0..a7f1020 100644
--- a/rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg
+++ b/rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg
@@ -3,7 +3,7 @@
#
%define gcc_version 4.8.3
-%define newlib_version ebbb290f6e15e71b140a911c0de530453b9f8443
+%define newlib_version b75c57950318ed657807f87a4c694e7b8d68fcae
This does not make sense to me. The config file name suggests this is a git
version of newlib so the hash is not used and should be ignored (and
removed). Git internally provides this type of functionality.
I believe the hash is used by RSB to set a specific commit to use.
+1
And I tested it, without this patch, it would get an earlier "buggy"
newlib version.
Sorry, my mistake. I thought was a hash value.
Chris
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
