Signed-off-by: Richard Purdie <[email protected]>
---
 meta/recipes-devtools/gcc/gcc/hardcoded-paths.patch     | 2 +-
 meta/recipes-devtools/gcc/gcc/prefix-map-realpath.patch | 3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/gcc/gcc/hardcoded-paths.patch 
b/meta/recipes-devtools/gcc/gcc/hardcoded-paths.patch
index aa3d16f6000..f3485858f48 100644
--- a/meta/recipes-devtools/gcc/gcc/hardcoded-paths.patch
+++ b/meta/recipes-devtools/gcc/gcc/hardcoded-paths.patch
@@ -1,7 +1,7 @@
 Avoid encoding build paths into sources used for floating point on powerpc.
 (MACHINE=qemuppc bitbake libgcc).
 
-Upstream-Status: Pending
+Upstream-Status: Submitted 
[https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599882.html]
 Signed-off-by: Richard Purdie <[email protected]>
 
 Index: gcc-12.1.0/libgcc/config/rs6000/t-float128
diff --git a/meta/recipes-devtools/gcc/gcc/prefix-map-realpath.patch 
b/meta/recipes-devtools/gcc/gcc/prefix-map-realpath.patch
index 3544f61a744..7f1a2deec7e 100644
--- a/meta/recipes-devtools/gcc/gcc/prefix-map-realpath.patch
+++ b/meta/recipes-devtools/gcc/gcc/prefix-map-realpath.patch
@@ -7,7 +7,8 @@ Instead, call gcc's realpath function on the incomming path 
name before
 comparing it with the remapping. This means other issues like symlinks
 are also accounted for and leads to a more consistent remapping experience.
 
-Upstream-Status: Pending [need to see if gcc developers would accept this]
+Upstream-Status: Submitted 
[https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599885.html]
+[Also https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599884.html]
 Signed-off-by: Richard Purdie <[email protected]>
 
 
-- 
2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#169490): 
https://lists.openembedded.org/g/openembedded-core/message/169490
Mute This Topic: https://lists.openembedded.org/mt/93082817/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to