Summary: | dev-qt/qtcore-4.8.4-r5 - .../work/qt-everywhere-opensource-src-4.8.4/config.tests/unix/glib/glib.cpp:53: riferimento non definito a "g_main_context_default" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fabio Coatti <fabio.coatti> |
Component: | [OLD] Library | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | de.techno, franz.trischberger |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 372079 | ||
Attachments: | build.log.gz |
Description
Fabio Coatti
2013-03-27 12:59:14 UTC
Please attach the entire build log to this bug report. Right, here you go :) Created attachment 343442 [details]
build.log.gz
According to the build log, the glib test misses to link against glib (no "-lglib-2.0"), hence the "undefined reference to "g_main_context_default" etc. additional info: * Found these USE flags for dev-libs/glib-2.34.3: U I - - debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see http://www.gentoo.org/proj/en/qa/backtraces.xml - - static-libs : Build static libraries - - systemtap : Build support for profiling and tracing using dev-util/systemtap - - test : Workaround to pull in packages needed to run with FEATURES=test. Portage-2.1.2 handles this internally, so don't set it in make.conf/package.use anymore - - utils : Install gtester-report utility to generate test report files for your software. + + xattr : Adds support for extended attributes (filesystem-stored metadata) Can you try without all the -f*loop* flags in C(XX)FLAGS ? Done; with FLAGS="-march=native -mtune=native -O2 -pipe " CXXFLAGS="${CFLAGS}" the compilation goes fine, many thanks. However, I'm not sure if we can consider closed this bug: the package should compile fine even with those flags, no? Maybe this should be reported upstream? *** This bug has been marked as a duplicate of bug 417105 *** *** Bug 466480 has been marked as a duplicate of this bug. *** |