I apologize for this, but I've already lost the output of the failed compile. The error occurred on lines 352 and 353 of cmdoptns.cpp. GCC complained that it's illegal to have an array index right after a type-id with parens around it, so I have a patch here that fixes that for GCC 3.4. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 49798 [details, diff] Fixes problems in cmdoptns.cpp:352-353 for GCC 3.4
This bug still exists, can someone put that patch in portage please?
Here's the output of the failed compile: c++ -DHAVE_CONFIG_H -I. -I. -I. -I../src -I/usr/include/libxml2 -I../src -O2 -m64 -mmmx -momit-leaf-frame-pointer -pipe -ffast-math -fmerge-all-constants -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -c cmdoptns.cpp -fPIC -DPIC -o .libs/cmdoptns.lo cmdoptns.cpp: In constructor `ost::CommandOptionParse_impl::CommandOptionParse_impl(int, char**, char*, ost::CommandOption*)': cmdoptns.cpp:352: error: array bound forbidden after parenthesized type-id cmdoptns.cpp:352: note: try removing the parentheses around the type-id cmdoptns.cpp:353: error: array bound forbidden after parenthesized type-id cmdoptns.cpp:353: note: try removing the parentheses around the type-id make: *** [cmdoptns.lo] Error 1 !!! ERROR: dev-libs/commonc++-1.9.7-r4 failed. !!! Function src_compile, Line 34, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message.
Seriously guys, this bug was reported in JANUARY with a successful patch to fix it. It is now SEPTEMBER and the patch has not been included into portage. WTF?
Just had the same problem, grep'ed through /usr/portage for commonc++, and guess what: _Nothing_ depends on commonc++-*. Just move on to commoncpp2, it compiles cleanly with gcc3.4. I will file a bug and ask for removal of commonc++-*. Cheers!
Ok, we'll take this over to bug 115707. *** This bug has been marked as a duplicate of 115707 ***
