[haiku-bugs] Re: [Haiku] #12202: std::to_string fails in GCC 4.8.4
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Fri, 10 Jul 2015 10:59:33 -0000
#12202: std::to_string fails in GCC 4.8.4
-------------------------+----------------------------
Reporter: haiqu | Owner: nobody
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: - General | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
-------------------------+----------------------------
Comment (by bonefish):
Replying to [comment:3 pulkomandy]:
You can force enabling of it by using -D_GLIBCXX_USE_C99 in you command
line arguments, if the implementation of std::to_string is inlined in
header files. I did something similar with _GLIBCXX_USE_C99_MATH in the
WebKit port
(
https://github.com/haiku/webkit/blob/rebased/Source/cmake/OptionsHaiku.cmake)
so I could use std::isinf and a few other methods from #include <math>.
Aren't the _GLIBCXX_* only meant to be set via the configuration (created
when building gcc/the std C++ lib) or as a side effect of `-std` compiler
flags? After googling a bit, korli's explanation seems very plausible.
Replying to [comment:4 haiqu]:
Replying to [comment:1 bonefish]:
Your bug reports tend to lack essential information. Please always
provide the Haiku version (hrev, hybrid type) and in case of compilation
issues the command line and full output.
I've often wondered why some of this information isn't a required field
in the bug report form.
Since the bug tracker is also used for website and sysadmin issues, that
wouldn't work.
In any case it wasn't required here, it was a generic error in any
version of GCC 4.8.4 on Haiku.
Possibly, but unless you are an expert in the respective area, it is hard
to assess such things. So please just provide the info. E.g. in this case,
assuming the issue is indeed the complex.h header and we fix it and
rebuild the gcc packages, the general gcc version (4.8.4, you failed to
specify the exact one) will remain the same. So having at least the Haiku
hrev would be helpful information.
For future reference you can always assume a GCC2 hybrid system (unless
otherwise specified), and the latest hrev at the time of the report.
Besides that not everyone will read this or recall it, that isn't helpful
when a ticket grows older. Having to guess basic infos like the Haiku
revision after a few month is an unnecessary annoyance. Having all the
relevant information available, may save the developers time and helps to
get the issue fixed faster. If you haven't yet, please have a look at
[wiki:ReportingBugs].
--
Ticket URL: <
https://dev.haiku-os.org/ticket/12202#comment:7>
Haiku <
https://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
