This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.0 cannot compile pooma
Jeffrey Oldham <oldham@codesourcery.com> writes:
| 2) Create a separate <string.h> file.
|
| <string.h> = <cstring>
| using std::size_t;
| using std::memcpy;
| // ...
|
| <cstring> = namespace std {
| #include "/usr/include/string.h" /* fully-qualified path */
| }
|
| <cstring> must use a fully-qualified path rather than <string.h> to
| avoid infinite recursion.
|
| The latter comes closer to the standard but requires some additional
| work during creation to resolve the fully-qualified path.
On some plateforms (Robert Lipe could provide data) the actual paths
depends on the `-ansi -pedantic' or something like that.
Creating <string.h> in terms of <cstring> is what we're supposed to do
but...
-- Gaby
CodeSourcery, LLC http://www.codesourcery.com