Hi Koen! On Wed, Jul 15, 2015 at 10:11 AM, Koen Deforche <k...@emweb.be> wrote: > Hey, > > Since you're building your test case with a C++14 compiler, you probably > didn't build Wt with the same compile flags. > See the WT_CPP_11_MODE CMake flag for building Wt.
Thanks, good catch. My use of "-std=gnu++14" as a compile options does seem to be triggering this issue. (And yes, I did not explicitly build Wt with c++11 or c++14.) I recompiled my test app leaving that option out: C:\...\wt_test>g++ -o section section.cpp -lwt -lwthttp -lboost_date_time-mgw49-1_57 -lboost_filesystem-mgw49-1_57 -lboost_program_options-mgw49-1_57 -lboost_random-mgw49-1_57 -lboost_regex-mgw49-1_57 -lboost_system-mgw49-1_57 -lboost_thread-mgw49-mt-s-1_57 -lws2_32 -lwsock32 and the duplicate-section messages go away. So, problem solved! (For now.) By the way, I tried compiling with "-std=c++11", "-std=gnu++11", "-std=c++14", as well as "-std=gnu++14". They all trigger the duplicate-session messages; only leaving out the "-std" option does not. As a follow-up, does anyone understand what is going on here? I sure don't. The complaint appears to be about WApplication.obj and WMenu.obj (extracted from libwt.a). So it's not obvious why compiling my app with "-std=gnu++14" should affect a match / mismatch between two already compiled object files. (And why might internalPathChanged().connect() trigger the issue?) Also, if I do pursue rebuilding Wt with the WT_CPP_11_MODE option, would I have to similarly rebuild boost (and would anyone know offhand how to do it)? And if I at some point want to use c++14 (or c++11) and don't rebuild Wt, how much should I worry about the duplicate-section messages? Does anyone know whether they represent a substantive error, or can I blissfully ignore them. > Regards, > koen Thanks again for your help. K. Frank > 2015-07-15 16:06 GMT+02:00 K. Frank <kfrank2...@gmail.com>: >> >> Hello List! >> >> I get "duplicate section ... has different size" messages when I >> build a Wt application that contains (as far as I can tell) a call >> to: >> >> internalPathChanged().connect (...); >> ... >> Details: >> >> This is wt-3.3.3 built with mingw-w64 on 64-bit windows 7: >> >> C:\...\wt_test>g++ --version >> g++ (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 4.9.2 >> >> When I build (link) my test program, I get the following par of messages: >> >> C:\...\wt_test>g++ -std=gnu++14 -o section section.cpp -lwt >> -lwthttp -lboost_date_time-mgw49-1_57 -lboost_filesystem-mgw49-1_57 >> -lboost_program_options-mgw49-1_57 -lboost_random-mgw49-1_57 >> -lboost_regex-mgw49-1_57 -lboost_system-mgw49-1_57 >> -lboost_thread-mgw49-mt-s-1_57 -lws2_32 -lwsock32 >> C:/.../wt-3.3.3_install/WT/lib/../lib/libwt.a(WApplication.obj): >> duplicate section >> ... ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
