From 0f0b42896196315acfc636b1e535cda4ee283646 Mon Sep 17 00:00:00 2001
From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Date: Fri, 4 Mar 2022 09:18:39 +0100
Subject: [PATCH] libstdc++: vxworks: remove stray <iostream> include

There doesn't seem to be any reason for this TU to include
<iostream>, and it causes errors when the resulting libstdc++ is used
on our VxWorks 5.5 target - presumably because now libstdc++ itself
contains an instance of std::ios_base::Init. Which should be mostly
harmless, but apparently isn't, and from a QoI viewpoint should
probably be avoided anyway.

libstdc++-v3/ChangeLog:

	* config/locale/vxworks/ctype_members.cc: Remove <iostream>
	  include.
---
 libstdc++-v3/config/locale/vxworks/ctype_members.cc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/libstdc++-v3/config/locale/vxworks/ctype_members.cc b/libstdc++-v3/config/locale/vxworks/ctype_members.cc
index 82569d075c6..d8ca551078d 100644
--- a/libstdc++-v3/config/locale/vxworks/ctype_members.cc
+++ b/libstdc++-v3/config/locale/vxworks/ctype_members.cc
@@ -33,7 +33,6 @@
 #include <cstdlib>
 #include <cstring>
 #include <cstdio>
-#include <iostream>
 
 namespace std _GLIBCXX_VISIBILITY(default)
 {