Hide Forgot
Description of problem: gdb --version GNU gdb (GDB) Fedora 7.12-29.fc25 wrong gdb version test string in qmake test (gdb --version | sed -e 's,[^0-9][^0-9]*\([0-9]\)\.\([0-9]\).*,\1\2,;q') -gt 72 Version-Release number of selected component (if applicable): qmake-qt4 --version QMake version 2.01a Using Qt version 4.8.7 in /usr/lib64 qt-devel-1:4.8.7-18.fc25.x86_64 How reproducible: link qt4 app Steps to Reproduce: 1. qtcreator 2. new proj 3. build 4. check commant after link Actual results: wrong test test (gdb --version | sed -e 's,[^0-9][^0-9]*\([0-9]\)\.\([0-9]\).*,\1\2,;q') -gt 72 Expected results: 7.12 > 7.2 Additional info: Copy from log 13:47:42: Running steps for project qt4_qmake... 13:47:42: Starting: "/usr/bin/qmake-qt4" /home/maxim.prohorenko/src/simple_c_tests/qt4_qmake/qt4_qmake.pro -r -spec linux-g++ CONFIG+=debug 13:47:42: The process "/usr/bin/qmake-qt4" exited normally. 13:47:42: Starting: "/usr/bin/make" g++ -c -pipe -g -Wall -W -D_REENTRANT -DQT_CORE_LIB -DQT_SHARED -I/usr/lib64/qt4/mkspecs/linux-g++ -I../qt4_qmake -I/usr/include/QtCore -I/usr/include -I. -I../qt4_qmake -I. -o main.o ../qt4_qmake/main.cpp g++ -o qt4_qmake main.o -L/usr/lib64 -lQtCore -lpthread { test -n "" && DESTDIR="" || DESTDIR=.; } && test $(gdb --version | sed -e 's,[^0-9][^0-9]*\([0-9]\)\.\([0-9]\).*,\1\2,;q') -gt 72 && gdb --nx --batch --quiet -ex 'set confirm off' -ex "save gdb-index $DESTDIR" -ex quit 'qt4_qmake' && test -f qt4_qmake.gdb-index && objcopy --add-section '.gdb_index=qt4_qmake.gdb-index' --set-section-flags '.gdb_index=readonly' 'qt4_qmake' 'qt4_qmake' && rm -f qt4_qmake.gdb-index || true 13:47:43: The process "/usr/bin/make" exited normally. 13:47:43: Elapsed time: 00:01.
could you please attach a testcase so i can reproduce this issue? Thanks
in file /usr/lib64/qt4/mkspecs/features/unix/gdb_dwarf_index.prf: test \$\$(gdb --version | sed -e \'s,[^0-9][^0-9]*\\([0-9]\\)\\.\\([0-9]\\).*,\\1\\2,;q\') -gt 72 && \ ... Try run gdb --version GNU gdb (GDB) Fedora 8.0.1-26.fc26 test $(gdb --version | sed -e 's,[^0-9][^0-9]*\([0-9]\)\.\([0-9]\).*,\1\2,;q') -gt 72 ; echo $? 0 test $(gdb --version | sed -e 's,[^0-9][^0-9]*\([0-9]\)\.\([0-9]\).*,\1\2,;q') -gt 92 ; echo $? 1 test $(echo "GNU gdb (GDB) Fedora 7.12" | sed -e 's,[^0-9][^0-9]*\([0-9]\)\.\([0-9]\).*,\1\2,;q') -gt 72 ; echo $? 1 test $(echo "GNU gdb (GDB) Fedora 7.3" | sed -e 's,[^0-9][^0-9]*\([0-9]\)\.\([0-9]\).*,\1\2,;q') -gt 72 ; echo $? 0
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.