Overview
Features
Download
Documentation
Community
Add-Ons & Services

build errors in case std=c++11

Please post support and help requests here.

build errors in case std=c++11

Postby killerbot » 12 Sep 2012, 20:09

I saw there was a patch for similar build errors (to come in 1.4.4p1), so I applied those, but it still does NOT build with this flag on.
Code: Select all
g++-4.7  -Iinclude -I/home/killerbot/SelfBuild/poco-1.4.4/CppUnit/include -I/home/killerbot/SelfBuild/poco-1.4.4/Foundation/include -I/home/killerbot/SelfBuild/poco-1.4.4/XML/include -I/home/killerbot/SelfBuild/poco-1.4.4/Util/include -I/home/killerbot/SelfBuild/poco-1.4.4/Net/include -Wall -Wno-sign-compare -std=c++11 -DPOCO_BUILD_HOST=XIII  -D_XOPEN_SOURCE=500 -D_REENTRANT -D_THREAD_SAFE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -DPOCO_HAVE_FD_EPOLL -DPOCO_HAVE_IPv6  -g -D_DEBUG  -c src/NumberParser.cpp -o /home/killerbot/SelfBuild/poco-1.4.4/Foundation/obj/Linux/x86_64/debug_static/NumberParser.o
src/NumberParser.cpp: In static member function ‘static bool Poco::NumberParser::tryParse64(const string&, Poco::Int64&)’:
src/NumberParser.cpp:127:42: error: unable to find string literal operator ‘operator"" I64_FMT’
src/NumberParser.cpp: In static member function ‘static bool Poco::NumberParser::tryParseUnsigned64(const string&, Poco::UInt64&)’:
src/NumberParser.cpp:144:42: error: unable to find string literal operator ‘operator"" I64_FMT’
src/NumberParser.cpp: In static member function ‘static bool Poco::NumberParser::tryParseHex64(const string&, Poco::UInt64&)’:
src/NumberParser.cpp:161:42: error: unable to find string literal operator ‘operator"" I64_FMT’
src/NumberParser.cpp:162:1: warning: control reaches end of non-void function [-Wreturn-type]
src/NumberParser.cpp: In static member function ‘static bool Poco::NumberParser::tryParseUnsigned64(const string&, Poco::UInt64&)’:
src/NumberParser.cpp:145:1: warning: control reaches end of non-void function [-Wreturn-type]
src/NumberParser.cpp: In static member function ‘static bool Poco::NumberParser::tryParse64(const string&, Poco::Int64&)’:
src/NumberParser.cpp:128:1: warning: control reaches end of non-void function [-Wreturn-type]


I changed the build/config/Linux on the following lines
Code: Select all
CXXFLAGS        = -Wall -Wno-sign-compare -std=c++11

SYSFLAGS = -D_XOPEN_SOURCE=500 -D_REENTRANT -D_THREAD_SAFE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -DPOCO_HAVE_FD_EPOLL -DPOCO_HAVE_IPv6

the latter one : -DPOCO_HAVE_IPv6
the former one : -std=c++11

Any ideas, fixes ?
killerbot
 
Posts: 67
Joined: 03 Dec 2009, 12:55

Re: build errors in case std=c++11

Postby pjwhite » 13 Sep 2012, 12:40

I don't have any fixes, but I have just finished compiling poco trunk for Mac OS X 10.8 using CXXFLAGS = '-std=c++11 -stdlib=libc++'.

I have a few patches that I will attach soon.

I also used cmake, because the binaries produced by the ./configure linked funny. I didn't investigate why because I prefer working in cmake x 100.
pjwhite
 
Posts: 11
Joined: 30 Aug 2012, 04:45


Return to Support

Who is online

Users browsing this forum: No registered users and 1 guest