Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. use -v to see invocation ??

use -v to see invocation ??

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
3 Posts 2 Posters 571 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    Anonymous_Banned275
    wrote on last edited by
    #1

    use -v to see invocation

    I would like to see if this error can help me to solve
    the problem.

    How / where to "use -v" in Qt?

    :-1: error: linker command failed with exit code 1 (use -v to see invocation)
    
    JonBJ 1 Reply Last reply
    0
    • A Anonymous_Banned275

      use -v to see invocation

      I would like to see if this error can help me to solve
      the problem.

      How / where to "use -v" in Qt?

      :-1: error: linker command failed with exit code 1 (use -v to see invocation)
      
      JonBJ Offline
      JonBJ Offline
      JonB
      wrote on last edited by JonB
      #2

      @AnneRanch
      I cannot test. I don't know if it can be done a better way or somewhere specific in Creator, but I think that if you edit your .pro to add line

      QMAKE_LFLAGS += -v
      

      and then re-run qmake from menu/complete rebuild that would now pass -v to linker/ld.

      Yep, even 10 years ago someone said

      After looking carefully at what is going on - Doing a "Clean All" and then rebuild through Qt Creator is not sufficient to pick up any changes to the linker flags such as those provided by the QMAKE_LFLAGS entry in the .pro file.

      You need to actually delete the entire debug / delete build directory, and then do a rebuild.

      So You need to actually delete the entire debug / delete build directory, and then do a rebuild. ! But another guy there claims

      Another option is to re-run qmake after you have changed .pro file.

      If not it's not the right way to do it but

      LIBS += -v
      

      might do it.

      However, even without -v argument to ld, doesn't Creator's "Build Output" pane already show the complete command-line invocation anyway, so you won't find out any more even if you pass -v to ld?

      A 1 Reply Last reply
      0
      • JonBJ JonB

        @AnneRanch
        I cannot test. I don't know if it can be done a better way or somewhere specific in Creator, but I think that if you edit your .pro to add line

        QMAKE_LFLAGS += -v
        

        and then re-run qmake from menu/complete rebuild that would now pass -v to linker/ld.

        Yep, even 10 years ago someone said

        After looking carefully at what is going on - Doing a "Clean All" and then rebuild through Qt Creator is not sufficient to pick up any changes to the linker flags such as those provided by the QMAKE_LFLAGS entry in the .pro file.

        You need to actually delete the entire debug / delete build directory, and then do a rebuild.

        So You need to actually delete the entire debug / delete build directory, and then do a rebuild. ! But another guy there claims

        Another option is to re-run qmake after you have changed .pro file.

        If not it's not the right way to do it but

        LIBS += -v
        

        might do it.

        However, even without -v argument to ld, doesn't Creator's "Build Output" pane already show the complete command-line invocation anyway, so you won't find out any more even if you pass -v to ld?

        A Offline
        A Offline
        Anonymous_Banned275
        wrote on last edited by
        #3

        @JonB said in use -v to see invocation ??:

        LIBS += -v

        Adding to .pro , either way, did not show and more erro details .

        Here is the latest snippet of the output

        make[1]: Leaving directory '/mnt/A_BT_DEC10/BT__PROGRAMS/A_MAR7_MAR15/A_MAR7_MAR17/TEST_PROJECT'
        /usr/bin/ld: /usr/bin/ld: DWARF error: invalid or unhandled FORM value: 0x23
        mainwindow.o: in function MainWindow::menu_slot_indexed(int)': mainwindow.cpp:(.text+0x965b): undefined reference to terminal_ORIGINAL_MainWindow::terminal_ORIGINAL_MainWindow(QWidget*)'
        clang: error: linker command failed with exit code 1 (use -v to see invocation)
        make[1]: Leaving directory '/mnt/A_BT_DEC10/BT__PROGRAMS/A_MAR7_MAR15/A_BT_LIBRARY/mdi'
        make[1]: *** [Makefile:293: mdi] Error 1
        make: *** [Makefile:596: sub----A_BT_LIBRARY-mdi-make_first] Error 2
        13:41:19: The process "/usr/bin/make" exited with code 2.
        Error while building/deploying project A_Mar7_MAR17 (kit: Qt 5.15.2 (gcc_64))
        When executing step "Make"
        13:41:19: Elapsed time: 00:29.

        there is one more not analyzed error :

        /usr/bin/ld: /usr/bin/ld: DWARF error: invalid or unhandled FORM value: 0x23

        I could use some help with

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved