>>> Emerging (1 of 1) app-crypt/qca-2.0.1-r1 * qca-2.0.1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking qca-2.0.1.tar.bz2 to /home/tmp/portage/app-crypt/qca-2.0.1-r1/work * Applying qca-2.0.1-pcfilespath.patch ... [ ok ] >>> Source unpacked. >>> Compiling source in /home/tmp/portage/app-crypt/qca-2.0.1-r1/work/qca-2.0.1 ... * Processing qmake qca.pro ... [ ok ] Configuring Qt Cryptographic Architecture (QCA) ... Verifying Qt 4 build environment ... yacc.prf:27: Unknown replace function: escape_expand yacc.prf:27: Unknown replace function: escape_expand yacc.prf:27: Unknown replace function: escape_expand yacc.prf:27: Unknown replace function: escape_expand yacc.prf:38: Unknown replace function: escape_expand lex.prf:19: Unknown replace function: escape_expand lex.prf:19: Unknown replace function: escape_expand lex.prf:19: Unknown replace function: escape_expand ./configure: line 2050: .qconftemp/conf: Datei oder Verzeichnis nicht gefunden fail Reason: Unexpected error launching 'conf' * * ERROR: app-crypt/qca-2.0.1-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2638: Called die * The specific snippet of code: * ./configure --prefix=/usr --qtdir=/usr --includedir="/usr/include/qca2" --libdir="/usr/${_libdir}/qca2" --no-separate-debug-info --disable-tests ${myconf} || die "configure failed"; * The die message: * configure failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/home/tmp/portage/app-crypt/qca-2.0.1-r1/temp/build.log'. * The ebuild environment file is located at '/home/tmp/portage/app-crypt/qca-2.0.1-r1/temp/environment'. * >>> Failed to emerge app-crypt/qca-2.0.1-r1, Log file: >>> '/home/tmp/portage/app-crypt/qca-2.0.1-r1/temp/build.log' app-crypt/qca-2.0.0-r2 fails with the same error Reproducible: Always Steps to Reproduce: 1. emerge app-crypt/qca
Looks like a yacc issue to me?
(In reply to comment #1) > Looks like a yacc issue to me? > escape_expand is something used inside qt. The problem is somewhere in the configure script: c -DHAVE_MODULES -DQT_NO_DEBUG -DQT_CORE_LIB -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/QtCore -I. -I. -o conf4.o conf4.cpp gmake: c: Kommando nicht gefunden gmake: [conf4.o] Fehler 127 (ignoriert) o conf conf4.o -lQtCore gmake: o: Kommando nicht gefunden gmake: [conf] Fehler 127 (ignoriert This is the output in conf.log
Ok, I've found the bug. The configure script calls /usr/bin/qmake4 which is from Qt version 4.1.3. It seems that this wasn't deleted when upgrading Qt. After removing /usr/bin/qmake4, /usr/bin/qmake from Qt version 4.4.2 is used and qca compiles fine. So it's not a qca-bug but a portage-bug I think.
(In reply to comment #3) > Ok, I've found the bug. The configure script calls /usr/bin/qmake4 which is > from Qt version 4.1.3. It seems that this wasn't deleted when upgrading Qt. > After removing /usr/bin/qmake4, /usr/bin/qmake from Qt version 4.4.2 is used > and qca compiles fine. > So it's not a qca-bug but a portage-bug I think. I can't reproduce it.
