Remove older GCC support
Signed-off-by: Manjukumar Matha
---
recipes-microblaze/gcc/gcc-source_4.9.bbappend | 7 ---
recipes-microblaze/gcc/gcc-source_5.3.bbappend | 8
2 files changed, 15 deletions(-)
delete mode 100644
This patch is applied upstream, and no longer required
Signed-off-by: Manjukumar Matha
---
.../gcc/files/microblaze-musl-support.patch| 44 --
1 file changed, 44 deletions(-)
delete mode 100644
Remove support for patches and GCC that are no longer supported in oe-core
upstream
Manjukumar Matha (2):
Remove old references to GCC 4.9 and 5.3
Remove this patch as it is no longer required
.../gcc/files/microblaze-musl-support.patch| 44 --
MB is failing to compile stating "ret" variable is a register. However renaming
the variable from ret to any other name fixes this issue. I think it might be a
GCC issue, but I am unable to re-create this corner case to report it to GCC.
Signed-off-by: Manjukumar Matha
Copy compiler-gcc5.h as compiler-gcc6.h to fix compilation error This is a
temporary fix till Xilinx u-boot gets updated
Upstream Status: Never
Signed-off-by: Manjukumar Matha
---
...compiler-gcc6.h-Fix-u-boot-issue-for-gcc6.patch | 92
Include the patch to fix compilation error due to missing header file
Signed-off-by: Manjukumar Matha
---
recipes-bsp/u-boot/u-boot-xlnx_2016.01.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/recipes-bsp/u-boot/u-boot-xlnx_2016.01.bb
Update Xilinx kernel recipe to xilinx-v2016.2 tag
Signed-off-by: Manjukumar Matha
---
recipes-kernel/linux/linux-xlnx_4.4.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-kernel/linux/linux-xlnx_4.4.bb
Update ATF recipe to xilinx-v2016.2 tag
Signed-off-by: Manjukumar Matha
---
recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi,
Looks like you might be stuck inside an internal corporate network
which doesn't not allow direct access to the public internet. Which is
why you are getting a "Connection reset by peer" error from git. You
will need to figure out what setup you have for your company and then
configure access