Most of us when port something with recent gcc, offten meet with issues when one or another function bring errors like "error: ‘func()’ is not a member of ‘std’".

Lately found that not only stoi(), but also stod(), stof(), stoul() and stol() can't be used as "not a members of std".

Doing some search, i found few files like this:

include\c++\8.2.0\bits\basic_string.h
include\c++\8.2.0\ext\vstring.h

Where we can see something like this (copy from vstring.h):




So, by logic enabling of _GLIBCXX_USE_C99_STDLIB should did the trick and they should work, but sadly just adding

#define _GLIBCXX_USE_C99_STDLIB 1

to include/c++/8.2.0/bits/c++config.h do not help.

It all just looks like it all can and should works, just in our GCC something not enabled or so..

Or maybe someone have some easy typedef which can be used instead ? Like something of that sort:



Any ideas and help apprecated, thanks!

@All
At moment found solution myself, a bit not clean as it , but still, maybe someone will have needs for:

To make those functions works without any code changes, you can add "-D_GLIBCXX_USE_C99_STDLIB" to makefile when compile objects, as well, as on linking stage you will have needs to add -lstdc++ too.

For example that test case:



Didn't work when we just do "ppc-amigaos-gcc test.cpp", and bring usual " error: ‘stoi’ is not a member of ‘std’", but then, if we do:

ppc-amigaos-gcc -D_GLIBCXX_USE_C99_STDLIB test.cpp , then object compiles fine, just linking fail, which we fix by adding -lstdc++ (together with our -athread=native and -lpthread).

So to summorize to compile that test case and make it works we do:

ppc-amigaos-gcc -D_GLIBCXX_USE_C99_STDLIB test.cpp -athread=native -lpthread -lstdc++

Of course we can use #define _GLIBCXX_USE_C99_STDLIB 1 in source code as well, or (by logic) in that c++config.h in our includes, but that sometime may not work, as seems some other includes also redefine it somehow.

That at least help with functions i check: stoi, stol, stod, stoul & stof. All compiles and links fine without code changes.

@kas1e

Those functions should be available with -std=c++11 (or higher).

Hans

@Hans
Yeah, they should, same as to_string(), basic_string(), etc. But as we all found , it is not.

So it can be some misconfiguration or misdefines of our latest gcc.

Remember that you have yourself the same problem, just with to_string() not being member of std :

https://github.com/sba1/adtools/issues/58

And that one you fix by enabling _GLIBCXX_USE_C99_STDIO. While those ones with stoi and co, fixed by adding by enabling _GLIBCXX_USE_C99_STDLIB.

In all cases , not c++11, not gnu++11 or whatever else didn't work. And i am somehow sure it is something in gcc configured wrong.

@kas1e

Ah yes, that's a mistake in the newlib headers. IIRC, it works correctly if you use clib2.

Hans

@Hans
If use clib2, then your issue about to_string() is gone, yes, but with stoi() and co, issue still here even with clib2.

My bet is not only newlib headers guilty (maybe with case of to_string() only newlib ), but also pure gcc includes as well (that c++config.h file, etc).