Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 345002 Details for
Bug 465284
media-libs/herqq-1.0.0-r1 build fails with bad qmake usage.
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
Build log from failing build
media-libs:herqq-1.0.0-r1:20130409-105552.log (text/plain), 8.92 KB, created by
Richard Ash
on 2013-04-09 15:42:17 UTC
(
hide
)
Description:
Build log from failing build
Filename:
MIME Type:
Creator:
Richard Ash
Created:
2013-04-09 15:42:17 UTC
Size:
8.92 KB
patch
obsolete
>[32;01m * [39;49;00mPackage: media-libs/herqq-1.0.0-r1 >[32;01m * [39;49;00mRepository: gentoo >[32;01m * [39;49;00mMaintainer: kde@gentoo.org >[32;01m * [39;49;00mUSE: abi_x86_32 elibc_glibc kernel_linux userland_GNU x86 >[32;01m * [39;49;00mFEATURES: preserve-libs sandbox userpriv usersandbox >>>> Unpacking source... >>>> Unpacking herqq-1.0.0.zip to /var/tmp/portage/media-libs/herqq-1.0.0-r1/work >>>> Source unpacked in /var/tmp/portage/media-libs/herqq-1.0.0-r1/work >>>> Preparing source in /var/tmp/portage/media-libs/herqq-1.0.0-r1/work/herqq-1.0.0 ... >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/media-libs/herqq-1.0.0-r1/work/herqq-1.0.0 ... > [32;01m*[0m Running qmake ... >[A[76C [34;01m[ [32;01mok[34;01m ][0m >>>> Source configured. >>>> Compiling source in /var/tmp/portage/media-libs/herqq-1.0.0-r1/work/herqq-1.0.0 ... >make -j3 -l 2.0 >cd hupnp/ && /usr/bin/qmake /var/tmp/portage/media-libs/herqq-1.0.0-r1/work/herqq-1.0.0/hupnp/hupnp.pro QTDIR=/usr/lib QMAKE=/usr/bin/qmake QMAKE_AR=i686-pc-linux-gnu-ar\ cqs QMAKE_CC=i686-pc-linux-gnu-gcc QMAKE_CXX=i686-pc-linux-gnu-g++ QMAKE_LINK=i686-pc-linux-gnu-g++ QMAKE_LINK_C=i686-pc-linux-gnu-gcc QMAKE_OBJCOPY=i686-pc-linux-gnu-objcopy QMAKE_RANLIB= QMAKE_STRIP= QMAKE_CFLAGS=-O2\ -pipe\ -fomit-frame-pointer\ -march=i686\ -mfpmath=sse\ -mmmx\ -msse\ -msse2\ -msse3\ -msse4a\ -mabm QMAKE_CFLAGS_RELEASE= QMAKE_CFLAGS_DEBUG= QMAKE_CXXFLAGS=-O2\ -pipe\ -fomit-frame-pointer\ -march=i686\ -mfpmath=sse\ -mmmx\ -msse\ -msse2\ -msse3\ -msse4a\ -mabm QMAKE_CXXFLAGS_RELEASE= QMAKE_CXXFLAGS_DEBUG= QMAKE_LFLAGS=-Wl,-O1\ -Wl,--as-needed\ -Wl,--as-needed QMAKE_LFLAGS_RELEASE= QMAKE_LFLAGS_DEBUG= QMAKE_LIBDIR_QT=/usr/lib/qt4 QMAKE_LIBDIR_X11=/usr/lib QMAKE_LIBDIR_OPENGL=/usr/lib PREFIX=/usr/ -o Makefile >cd apps/simple_test-app/ && /usr/bin/qmake /var/tmp/portage/media-libs/herqq-1.0.0-r1/work/herqq-1.0.0/apps/simple_test-app/simple_test-app.pro QTDIR=/usr/lib QMAKE=/usr/bin/qmake QMAKE_AR=i686-pc-linux-gnu-ar\ cqs QMAKE_CC=i686-pc-linux-gnu-gcc QMAKE_CXX=i686-pc-linux-gnu-g++ QMAKE_LINK=i686-pc-linux-gnu-g++ QMAKE_LINK_C=i686-pc-linux-gnu-gcc QMAKE_OBJCOPY=i686-pc-linux-gnu-objcopy QMAKE_RANLIB= QMAKE_STRIP= QMAKE_CFLAGS=-O2\ -pipe\ -fomit-frame-pointer\ -march=i686\ -mfpmath=sse\ -mmmx\ -msse\ -msse2\ -msse3\ -msse4a\ -mabm QMAKE_CFLAGS_RELEASE= QMAKE_CFLAGS_DEBUG= QMAKE_CXXFLAGS=-O2\ -pipe\ -fomit-frame-pointer\ -march=i686\ -mfpmath=sse\ -mmmx\ -msse\ -msse2\ -msse3\ -msse4a\ -mabm QMAKE_CXXFLAGS_RELEASE= QMAKE_CXXFLAGS_DEBUG= QMAKE_LFLAGS=-Wl,-O1\ -Wl,--as-needed\ -Wl,--as-needed QMAKE_LFLAGS_RELEASE= QMAKE_LFLAGS_DEBUG= QMAKE_LIBDIR_QT=/usr/lib/qt4 QMAKE_LIBDIR_X11=/usr/lib QMAKE_LIBDIR_OPENGL=/usr/lib PREFIX=/usr/ -o Makefile >***Unknown option -mmmx -msse -msse2 -msse3 -msse4a -mabm >***Unknown option -mmmx -msse -msse2 -msse3 -msse4a -mabm >Usage: /usr/bin/qmake [mode] [options] [files] > >QMake has two modes, one mode for generating project files based on >some heuristics, and the other for generating makefiles. Normally you >shouldn't need to specify a mode, as makefile generation is the default >mode for qmake, but you may use this to test qmake on an existing project > >Mode: > -project Put qmake into project file generation mode > In this mode qmake interprets files as files to > be built, > defaults to *.c; *.ui; *.y; *.l; *.ts; *.xlf; *.qrc; *.h; *.hpp; *.hh; *.hxx; *.H; *.cpp; *.cc; *.cxx; *.C > Note: The created .pro file probably will > need to be edited. For example add the QT variable to > specify what modules are required. > -makefile Put qmake into makefile generation mode (default) > In this mode qmake interprets files as project files to > be processed, if skipped qmake will try to find a project > file in your current working directory > >Warnings Options: > -Wnone Turn off all warnings; specific ones may be re-enabled by > later -W options > -Wall Turn on all warnings > -Wparser Turn on parser warnings > -Wlogic Turn on logic warnings (on by default) > -Wdeprecated Turn on deprecation warnings (on by default) > >Options: > * You can place any variable assignment in options and it will be * > * processed as if it was in [files]. These assignments will be parsed * > * before [files]. * > -o file Write output to file > -d Increase debug level > -t templ Overrides TEMPLATE as templ > -tp prefix Overrides TEMPLATE so that prefix is prefixed into the value > -help This help > -v Version information > -after All variable assignments after this will be > parsed after [files] > -norecursive Don't do a recursive search > -recursive Do a recursive search > -set <prop> <value> Set persistent property > -unset <prop> Unset persistent property > -query <prop> Query persistent property. Show all if <prop> is empty. > -cache file Use file as cache [makefile mode only] > -spec spec Use spec as QMAKESPEC [makefile mode only] > -nocache Don't use a cache file [makefile mode only] > -nodepend Don't generate dependencies [makefile mode only] > -nomoc Don't generate moc targets [makefile mode only] > -nopwd Don't look for files in pwd [project mode only] >Usage: /usr/bin/qmake [mode] [options] [files] > >QMake has two modes, one mode for generating project files based on >some heuristics, and the other for generating makefiles. Normally you >shouldn't need to specify a mode, as makefile generation is the default >mode for qmake, but you may use this to test qmake on an existing project > >Mode: > -project Put qmake into project file generation mode > In this mode qmake interprets files as files to > be built, > defaults to *.c; *.ui; *.y; *.l; *.ts; *.xlf; *.qrc; *.h; *.hpp; *.hh; *.hxx; *.H; *.cpp; *.cc; *.cxx; *.C > Note: The created .pro file probably will > need to be edited. For example add the QT variable to > specify what modules are required. > -makefile Put qmake into makefile generation mode (default) > In this mode qmake interprets files as project files to > be processed, if skipped qmake will try to find a project > file in your current working directory > >Warnings Options: > -Wnone Turn off all warnings; specific ones may be re-enabled by > later -W options > -Wall Turn on all warnings > -Wparser Turn on parser warnings > -Wlogic Turn on logic warnings (on by default) > -Wdeprecated Turn on deprecation warnings (on by default) > >Options: > * You can place any variable assignment in options and it will be * > * processed as if it was in [files]. These assignments will be parsed * > * before [files]. * > -o file Write output to file > -d Increase debug level > -t templ Overrides TEMPLATE as templ > -tp prefix Overrides TEMPLATE so that prefix is prefixed into the value > -help This help > -v Version information > -after All variable assignments after this will be > parsed after [files] > -norecursive Don't do a recursive search > -recursive Do a recursive search > -set <prop> <value> Set persistent property > -unset <prop> Unset persistent property > -query <prop> Query persistent property. Show all if <prop> is empty. > -cache file Use file as cache [makefile mode only] > -spec spec Use spec as QMAKESPEC [makefile mode only] > -nocache Don't use a cache file [makefile mode only] > -nodepend Don't generate dependencies [makefile mode only] > -nomoc Don't generate moc targets [makefile mode only] > -nopwd Don't look for files in pwd [project mode only] >make: *** [apps/simple_test-app/Makefile] Error 1 >make: *** Waiting for unfinished jobs.... >make: *** [hupnp/Makefile] Error 1 > [31;01m*[0m ERROR: media-libs/herqq-1.0.0-r1 failed (compile phase): > [31;01m*[0m emake failed > [31;01m*[0m > [31;01m*[0m If you need support, post the output of `emerge --info '=media-libs/herqq-1.0.0-r1'`, > [31;01m*[0m the complete build log and the output of `emerge -pqv '=media-libs/herqq-1.0.0-r1'`. > [31;01m*[0m The complete build log is located at '/var/log/portage/media-libs:herqq-1.0.0-r1:20130409-105552.log'. > [31;01m*[0m For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/herqq-1.0.0-r1/temp/build.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/media-libs/herqq-1.0.0-r1/temp/environment'. > [31;01m*[0m Working directory: '/var/tmp/portage/media-libs/herqq-1.0.0-r1/work/herqq-1.0.0' > [31;01m*[0m S: '/var/tmp/portage/media-libs/herqq-1.0.0-r1/work/herqq-1.0.0'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 465284
: 345002