Opened 15 years ago
Closed 15 years ago
#1582 closed Bugs (fixed)
BOOST_HAS_LONG_LONG is defined when it shouldn't be
Reported by: | Steven Watanabe | Owned by: | John Maddock |
---|---|---|---|
Milestone: | Boost 1.36.0 | Component: | config |
Version: | Boost Development Trunk | Severity: | Problem |
Keywords: | Cc: |
Description
One of the units examples is now failing on gcc 3.4.4.
I'm compiling with <warnings>all which causes the options -Wall and -pedantic to be passed to the compiler. Apparently, -pedantic disables long long and boost/config/compiler/gcc.hpp fails to detect this.
Change History (5)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Actually, I'm not using long long at all. The error is coming from boost/type_traits/make_signed.hpp
comment:3 by , 15 years ago
Got it: I've just committed a fix to Trunk that allows all the type traits tests (and headers) to build with -Wall -pedantic.
Let me know if this fixes things.
John.
comment:5 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I was under the impression that long long was always supported by gcc, but that it would emit warnings (rather a lot of them actually) if you actually use it under some circumstances. We have the typedef's boost::long_long_type and boost::ulong_long_type in boost/config.hpp which can be used without generation of the warnings.
Otherwise what's the test case?
Thanks, John.