Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. QT5 build: CC: No such file or directory
Forum Updated to NodeBB v4.3 + New Features

QT5 build: CC: No such file or directory

Scheduled Pinned Locked Moved Unsolved Installation and Deployment
69 Posts 4 Posters 13.6k 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.
  • M Michele31415

    I've started doing that too. In any case, with this:

    /opt/qt5/qt5-build $ ../configure  -opensource -nomake examples -nomake tests -platform solaris-g++ -skip qtserialbus
    

    we're now going much further but are not there yet.

    /opt/qt5/qtbase/src/tools/moc/moc.cpp: In member function ‘void Moc::parseSlots(ClassDef*, FunctionDef::Access)’:
    /opt/qt5/qtbase/src/tools/moc/moc.cpp:1049:18: warning: this statement may fall through [-Wimplicit-fallthrough=]
     1049 |             error("'using' directive not supported in 'slots' section");
          |             ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    /opt/qt5/qtbase/src/tools/moc/moc.cpp:1050:9: note: here
     1050 |         default:
          |         ^~~~~~~
    /opt/qt5/qtbase/src/tools/moc/moc.cpp: In member function ‘void Moc::parseSignals(ClassDef*)’:
    /opt/qt5/qtbase/src/tools/moc/moc.cpp:1103:18: warning: this statement may fall through [-Wimplicit-fallthrough=]
     1103 |             error("'using' directive not supported in 'signals' section");
          |             ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    /opt/qt5/qtbase/src/tools/moc/moc.cpp:1104:9: note: here
     1104 |         default:
          |         ^~~~~~~
    

    Honestly, this error is mystifying.

    M Offline
    M Offline
    Michele31415
    wrote on last edited by
    #52

    Hah! That joke's on me. (From now on I'll search for "error:" instead of just "error") Here's the real error:

    ...
    In file included from /opt/qt5/qt3d/src/3rdparty/assimp/code/StreamReader.h:48,
                     from /opt/qt5/qt3d/src/3rdparty/assimp/code/AssimpPCH.h:151,
                     from /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:48:
    /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp: In instantiation of ‘std::size_t Assimp::Copy(uint8_t*, T&) [with T = short unsigned int; std::size_t = long unsigned int; uint8_t = unsigned char]’:
    /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:93:44:   required from here
    /opt/qt5/qt3d/src/3rdparty/assimp/code/ByteSwap.h:207:36: error: lvalue required as unary ‘&’ operand
      207 | # define AI_BE(t) ByteSwap::Swapped(t)
          |                   ~~~~~~~~~~~~~~~~~^~~
    /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:85:22: note: in expansion of macro ‘AI_BE’
       85 |   std::memcpy(data, &AI_BE(field), sizeof(field)); return sizeof(field);
          |                      ^~~~~
    /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp: In instantiation of ‘std::size_t Assimp::Copy(uint8_t*, T&) [with T = unsigned int; std::size_t = long unsigned int; uint8_t = unsigned char]’:
    /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:94:44:   required from here
    /opt/qt5/qt3d/src/3rdparty/assimp/code/ByteSwap.h:207:36: error: lvalue required as unary ‘&’ operand
      207 | # define AI_BE(t) ByteSwap::Swapped(t)
          |                   ~~~~~~~~~~~~~~~~~^~~
    /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:85:22: note: in expansion of macro ‘AI_BE’
       85 |   std::memcpy(data, &AI_BE(field), sizeof(field)); return sizeof(field);
          |                      ^~~~~
    /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp: In instantiation of ‘std::size_t Assimp::Copy(uint8_t*, T&) [with T = int; std::size_t = long unsigned int; uint8_t = unsigned char]’:
    /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:108:42:   required from here
    /opt/qt5/qt3d/src/3rdparty/assimp/code/ByteSwap.h:207:36: error: lvalue required as unary ‘&’ operand
      207 | # define AI_BE(t) ByteSwap::Swapped(t)
          |                   ~~~~~~~~~~~~~~~~~^~~
    /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:85:22: note: in expansion of macro ‘AI_BE’
       85 |   std::memcpy(data, &AI_BE(field), sizeof(field)); return sizeof(field);
          |                      ^~~~~
    gmake[4]: *** [Makefile:2840: .obj/Bitmap.o] Error 1
    gmake[4]: Leaving directory '/opt/qt5/qt5-build/qt3d/src/plugins/sceneparsers/assimp'
    gmake[3]: *** [Makefile:44: sub-assimp-make_first] Error 2
    gmake[3]: Leaving directory '/opt/qt5/qt5-build/qt3d/src/plugins/sceneparsers'
    gmake[2]: *** [Makefile:446: sub-plugins-sceneparsers-make_first] Error 2
    gmake[2]: Leaving directory '/opt/qt5/qt5-build/qt3d/src'
    gmake[1]: *** [Makefile:46: sub-src-make_first] Error 2
    gmake[1]: Leaving directory '/opt/qt5/qt5-build/qt3d'
    
    JonBJ 1 Reply Last reply
    0
    • M Michele31415

      Hah! That joke's on me. (From now on I'll search for "error:" instead of just "error") Here's the real error:

      ...
      In file included from /opt/qt5/qt3d/src/3rdparty/assimp/code/StreamReader.h:48,
                       from /opt/qt5/qt3d/src/3rdparty/assimp/code/AssimpPCH.h:151,
                       from /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:48:
      /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp: In instantiation of ‘std::size_t Assimp::Copy(uint8_t*, T&) [with T = short unsigned int; std::size_t = long unsigned int; uint8_t = unsigned char]’:
      /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:93:44:   required from here
      /opt/qt5/qt3d/src/3rdparty/assimp/code/ByteSwap.h:207:36: error: lvalue required as unary ‘&’ operand
        207 | # define AI_BE(t) ByteSwap::Swapped(t)
            |                   ~~~~~~~~~~~~~~~~~^~~
      /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:85:22: note: in expansion of macro ‘AI_BE’
         85 |   std::memcpy(data, &AI_BE(field), sizeof(field)); return sizeof(field);
            |                      ^~~~~
      /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp: In instantiation of ‘std::size_t Assimp::Copy(uint8_t*, T&) [with T = unsigned int; std::size_t = long unsigned int; uint8_t = unsigned char]’:
      /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:94:44:   required from here
      /opt/qt5/qt3d/src/3rdparty/assimp/code/ByteSwap.h:207:36: error: lvalue required as unary ‘&’ operand
        207 | # define AI_BE(t) ByteSwap::Swapped(t)
            |                   ~~~~~~~~~~~~~~~~~^~~
      /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:85:22: note: in expansion of macro ‘AI_BE’
         85 |   std::memcpy(data, &AI_BE(field), sizeof(field)); return sizeof(field);
            |                      ^~~~~
      /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp: In instantiation of ‘std::size_t Assimp::Copy(uint8_t*, T&) [with T = int; std::size_t = long unsigned int; uint8_t = unsigned char]’:
      /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:108:42:   required from here
      /opt/qt5/qt3d/src/3rdparty/assimp/code/ByteSwap.h:207:36: error: lvalue required as unary ‘&’ operand
        207 | # define AI_BE(t) ByteSwap::Swapped(t)
            |                   ~~~~~~~~~~~~~~~~~^~~
      /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp:85:22: note: in expansion of macro ‘AI_BE’
         85 |   std::memcpy(data, &AI_BE(field), sizeof(field)); return sizeof(field);
            |                      ^~~~~
      gmake[4]: *** [Makefile:2840: .obj/Bitmap.o] Error 1
      gmake[4]: Leaving directory '/opt/qt5/qt5-build/qt3d/src/plugins/sceneparsers/assimp'
      gmake[3]: *** [Makefile:44: sub-assimp-make_first] Error 2
      gmake[3]: Leaving directory '/opt/qt5/qt5-build/qt3d/src/plugins/sceneparsers'
      gmake[2]: *** [Makefile:446: sub-plugins-sceneparsers-make_first] Error 2
      gmake[2]: Leaving directory '/opt/qt5/qt5-build/qt3d/src'
      gmake[1]: *** [Makefile:46: sub-src-make_first] Error 2
      gmake[1]: Leaving directory '/opt/qt5/qt5-build/qt3d'
      
      JonBJ Offline
      JonBJ Offline
      JonB
      wrote on last edited by JonB
      #53

      @Michele31415 said in QT5 build: CC: No such file or directory:

      /opt/qt5/qt3d/src/3rdparty/assimp/code/Bitmap.cpp: In instantiation of ‘std::size_t Assimp::Copy(uint8_t*, T&) [with T = short unsigned int; std::size_t = long unsigned int; uint8_t = unsigned char]’:

      I couldn't help searching :) https://github.com/ros/meta-ros/issues/526, in 2017

      assimp: "error: lvalue required as unary '&' operand" on mips, mips64 and ppc

      | /home/lukas/work/repositories/yoctoproject.org/poky/build/tmp/work/mips32r2-poky-linux/assimp/3.1.1-r0/assimp-3.1.1/code/Bitmap.cpp: In instantiation of 'std::size_t Assimp::Copy(uint8_t*, T&) [with T = short unsigned int; std::size_t = unsigned int; uint8_t = unsigned char]':

      Dunno what you're supposed to do about it though? :)

      I think your error has also been reported in this forum:
      Qt 5.7.1 build in Debian (MIPS) fails.

      @SGaist was going to deal with that topic back in 2017 :)

      1 Reply Last reply
      0
      • M Offline
        M Offline
        Michele31415
        wrote on last edited by
        #54

        "Dunno what you're supposed to do about it though? :)"
        Well that makes two of us. In my own search, this seems to suggest it's a programming error:
        https://stackoverflow.com/questions/22788026/error-lvalue-required-as-unary-operand
        How sayest thou, O great Gaist?

        JonBJ 1 Reply Last reply
        0
        • M Michele31415

          "Dunno what you're supposed to do about it though? :)"
          Well that makes two of us. In my own search, this seems to suggest it's a programming error:
          https://stackoverflow.com/questions/22788026/error-lvalue-required-as-unary-operand
          How sayest thou, O great Gaist?

          JonBJ Offline
          JonBJ Offline
          JonB
          wrote on last edited by
          #55

          @Michele31415
          :)
          Yes, it's a programming error in the code which only shows up on certain architectures. Why it has not been picked up in whatever version you are building (which is that?) I do not know.

          While building qt5 in Solaris 11.4 SPARC, I get:

          Not that I know about these things, but then are you "MIPS"?

          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #56

            @JonB said in QT5 build: CC: No such file or directory:

            Not that I know about these things, but then are you "MIPS"?

            Nop, he's SPARC.

            As for that issue, coming from ASSIMP, it's likely something you should bring to their folks.

            Sadly I do not have a big endian machine to check further what is going on there.

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            M 2 Replies Last reply
            1
            • SGaistS SGaist

              @JonB said in QT5 build: CC: No such file or directory:

              Not that I know about these things, but then are you "MIPS"?

              Nop, he's SPARC.

              As for that issue, coming from ASSIMP, it's likely something you should bring to their folks.

              Sadly I do not have a big endian machine to check further what is going on there.

              M Offline
              M Offline
              Michele31415
              wrote on last edited by Michele31415
              #57

              @SGaist "Sadly I do not have a big endian machine to check further what is going on there."
              Would you like an account on my machine? It's a Sun T4-1 with plenty of spare CPU cycles and a fast fiber connection. Consider it my contribution to the QT project.

              1 Reply Last reply
              0
              • SGaistS SGaist

                @JonB said in QT5 build: CC: No such file or directory:

                Not that I know about these things, but then are you "MIPS"?

                Nop, he's SPARC.

                As for that issue, coming from ASSIMP, it's likely something you should bring to their folks.

                Sadly I do not have a big endian machine to check further what is going on there.

                M Offline
                M Offline
                Michele31415
                wrote on last edited by
                #58

                @SGaist I decided to press on, using the "scorched earth" method. Every time I hit an error I just commented it out. Turns out there were only two more places, in MathExtras.h. I now have a build that contains no instances of "error:". It ends thusly:

                ...
                moc_qscriptdebuggercodefinderwidgetinterface_p.o .obj/moc_qscriptdebugoutputwidgetinterface_p.o .obj/moc_qscriptdebugoutputwidget_p.o .obj/moc_qscriptbreakpointswidgetinterface_p.o .obj/moc_qscriptbreakpointsmodel_p.o .obj/moc_qscripterrorlogwidgetinterface_p.o .obj/moc_qscripterrorlogwidget_p.o  -L/usr/sfw/lib -L/usr/openwin/lib -L/opt/qt5/qt5-build/qtbase/lib -lQt5Core -lpthread -lrt -lQt5Widgets -L/usr/sfw/lib -L/usr/openwin/lib -L/opt/qt5/qt5-build/qtbase/lib -lQt5Gui -L/opt/qt5/qt5-build/qtscript/lib -lQt5Script -lQt5Core -lpthread -lrt -lGL 
                ln -s libQt5ScriptTools.so.5.8.0 libQt5ScriptTools.so
                ln -s libQt5ScriptTools.so.5.8.0 libQt5ScriptTools.so.5
                ln -s libQt5ScriptTools.so.5.8.0 libQt5ScriptTools.so.5.8
                rm -f ../../lib/libQt5ScriptTools.so.5.8.0
                mv -f libQt5ScriptTools.so.5.8.0  ../../lib/ 
                rm -f ../../lib/libQt5ScriptTools.so
                rm -f ../../lib/libQt5ScriptTools.so.5
                rm -f ../../lib/libQt5ScriptTools.so.5.8
                mv -f libQt5ScriptTools.so ../../lib/ 
                mv -f libQt5ScriptTools.so.5 ../../lib/ 
                mv -f libQt5ScriptTools.so.5.8 ../../lib/ 
                gmake[3]: Leaving directory '/opt/qt5/qt5-build/qtscript/src/scripttools'
                gmake[2]: Leaving directory '/opt/qt5/qt5-build/qtscript/src'
                gmake[1]: Leaving directory '/opt/qt5/qt5-build/qtscript'
                

                Is there some way to test it to see if it works?

                M 1 Reply Last reply
                0
                • M Michele31415

                  @SGaist I decided to press on, using the "scorched earth" method. Every time I hit an error I just commented it out. Turns out there were only two more places, in MathExtras.h. I now have a build that contains no instances of "error:". It ends thusly:

                  ...
                  moc_qscriptdebuggercodefinderwidgetinterface_p.o .obj/moc_qscriptdebugoutputwidgetinterface_p.o .obj/moc_qscriptdebugoutputwidget_p.o .obj/moc_qscriptbreakpointswidgetinterface_p.o .obj/moc_qscriptbreakpointsmodel_p.o .obj/moc_qscripterrorlogwidgetinterface_p.o .obj/moc_qscripterrorlogwidget_p.o  -L/usr/sfw/lib -L/usr/openwin/lib -L/opt/qt5/qt5-build/qtbase/lib -lQt5Core -lpthread -lrt -lQt5Widgets -L/usr/sfw/lib -L/usr/openwin/lib -L/opt/qt5/qt5-build/qtbase/lib -lQt5Gui -L/opt/qt5/qt5-build/qtscript/lib -lQt5Script -lQt5Core -lpthread -lrt -lGL 
                  ln -s libQt5ScriptTools.so.5.8.0 libQt5ScriptTools.so
                  ln -s libQt5ScriptTools.so.5.8.0 libQt5ScriptTools.so.5
                  ln -s libQt5ScriptTools.so.5.8.0 libQt5ScriptTools.so.5.8
                  rm -f ../../lib/libQt5ScriptTools.so.5.8.0
                  mv -f libQt5ScriptTools.so.5.8.0  ../../lib/ 
                  rm -f ../../lib/libQt5ScriptTools.so
                  rm -f ../../lib/libQt5ScriptTools.so.5
                  rm -f ../../lib/libQt5ScriptTools.so.5.8
                  mv -f libQt5ScriptTools.so ../../lib/ 
                  mv -f libQt5ScriptTools.so.5 ../../lib/ 
                  mv -f libQt5ScriptTools.so.5.8 ../../lib/ 
                  gmake[3]: Leaving directory '/opt/qt5/qt5-build/qtscript/src/scripttools'
                  gmake[2]: Leaving directory '/opt/qt5/qt5-build/qtscript/src'
                  gmake[1]: Leaving directory '/opt/qt5/qt5-build/qtscript'
                  

                  Is there some way to test it to see if it works?

                  M Offline
                  M Offline
                  Michele31415
                  wrote on last edited by
                  #59

                  Hearing nothing I decided to press on. gmake install did not go well:

                  root@hemlock:/opt/qt5/qt5-build# gmake install
                  cd qtbase/ && ( test -e Makefile || /opt/qt5/qt5-build/qtbase/bin/qmake -o Makefile /opt/qt5/qtbase/qtbase.pro -qtconf /opt/qt5/qt5-build/qtbase/bin/qt.conf -- -opensource -nomake examples -nomake tests -platform solaris-g++ -skip qtserialbus ) && gmake -f Makefile install
                  gmake[1]: Entering directory '/opt/qt5/qt5-build/qtbase'
                  cd src/ && ( test -e Makefile || /opt/qt5/qt5-build/qtbase/bin/qmake -o Makefile /opt/qt5/qtbase/src/src.pro -qtconf /opt/qt5/qt5-build/qtbase/bin/qt.conf -- -opensource -nomake examples -nomake tests -platform solaris-g++ -skip qtserialbus ) && gmake -f Makefile install
                  gmake[2]: Entering directory '/opt/qt5/qt5-build/qtbase/src'
                  cd tools/bootstrap/ && ( test -e Makefile || /opt/qt5/qt5-build/qtbase/bin/qmake -o Makefile /opt/qt5/qtbase/src/tools/bootstrap/bootstrap.pro -qtconf /opt/qt5/qt5-build/qtbase/bin/qt.conf -- -opensource -nomake examples -nomake tests -platform solaris-g++ -skip qtserialbus ) && gmake -f Makefile install
                  gmake[3]: Entering directory '/opt/qt5/qt5-build/qtbase/src/tools/bootstrap'
                  install -m 644 -p ../../../lib/libQt5Bootstrap.a /lib/libQt5Bootstrap.a
                  find: stat() error /lib/libQt5Bootstrap.a: No such file or directory
                  find: stat() error /bin/pod2man: Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS
                  find: stat() error /usr/bin/pod2man: Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS
                  find: cycle detected for /lib/secure/32/
                  find: cycle detected for /lib/crypto/32/
                  find: cycle detected for /lib/32/
                  find: cycle detected for /lib/fm/32/
                  find: cycle detected for /usr/lib/gss/32/
                  find: cycle detected for /usr/lib/pool/32/
                  find: cycle detected for /usr/lib/python2.7/vendor-packages/nss/32/
                  find: cycle detected for /usr/lib/python2.7/vendor-packages/solaris/32/
                  find: cycle detected for /usr/lib/python2.7/vendor-packages/zfs/32/
                  find: cycle detected for /usr/lib/reparse/32/
                  find: cycle detected for /usr/lib/secure/32/
                  find: cycle detected for /usr/lib/brand/solaris10/32/
                  find: cycle detected for /usr/lib/32/
                  find: cycle detected for /usr/lib/scsi/32/
                  find: cycle detected for /usr/lib/lwp/32/
                  find: cycle detected for /usr/lib/fm/topo/plugins/32/
                  find: cycle detected for /usr/lib/fm/32/
                  find: cycle detected for /usr/lib/rad/client/c/32/
                  find: cycle detected for /usr/lib/cfgadm/32/
                  find: cycle detected for /usr/lib/locale/en_US.UTF-8/32/
                  find: cycle detected for /usr/lib/locale/en_US.UTF-8/LO_LTYPE/32/
                  find: cycle detected for /usr/lib/locale/en_US.UTF-8/LC_CTYPE/32/
                  find: cycle detected for /usr/lib/security/32/
                  find: cycle detected for /usr/lib/link_audit/32/
                  find: cycle detected for /usr/lib/nfs/32/
                  find: cycle detected for /usr/lib/elfedit/32/
                  install: -p was not found anywhere!
                  gmake[3]: [Makefile:9516: install_target] Error 2 (ignored)
                  sed -e 's,[^ '\'']*/opt/qt5/qt5-build/[^/][^/]*/lib,,g' ../../../lib/libQt5Bootstrap.prl > /lib/libQt5Bootstrap.prl
                  sed -e 's,[^ '\'']*/opt/qt5/qt5-build/[^/][^/]*/lib,,g' ../../../lib/libQt5Bootstrap.la > /lib/libQt5Bootstrap.la
                  install -m 644 -p /opt/qt5/qt5-build/qtbase/mkspecs/modules-inst/qt_lib_bootstrap_private.pri //mkspecs/modules/
                  find: stat() error /bin/pod2man: Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS
                  find: stat() error /usr/bin/pod2man: Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS
                  find: cycle detected for /lib/secure/32/
                  ...etc...
                  
                  1 Reply Last reply
                  0
                  • SGaistS Offline
                    SGaistS Offline
                    SGaist
                    Lifetime Qt Champion
                    wrote on last edited by
                    #60

                    Don't do that kind of things as root, you might break stuff ;-)

                    One thing I would do is to just build and install qtbase so you have a working base to go further.

                    Interested in AI ? www.idiap.ch
                    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                    1 Reply Last reply
                    0
                    • M Offline
                      M Offline
                      Michele31415
                      wrote on last edited by
                      #61

                      I thought gmake install always had to be done as root. In any case, it works even less as ordinary user in qtbase:

                      /opt/qt5/qt5-build/qtbase $ gmake install
                      cd src/ && ( test -e Makefile || /opt/qt5/qt5-build/qtbase/bin/qmake -o Makefile /opt/qt5/qtbase/src/src.pro -qtconf /opt/qt5/qt5-build/qtbase/bin/qt.conf -- -opensource -nomake examples -nomake tests -platform solaris-g++ -skip qtserialbus ) && gmake -f Makefile install
                      gmake[1]: Entering directory '/opt/qt5/qt5-build/qtbase/src'
                      cd tools/bootstrap/ && ( test -e Makefile || /opt/qt5/qt5-build/qtbase/bin/qmake -o Makefile /opt/qt5/qtbase/src/tools/bootstrap/bootstrap.pro -qtconf /opt/qt5/qt5-build/qtbase/bin/qt.conf -- -opensource -nomake examples -nomake tests -platform solaris-g++ -skip qtserialbus ) && gmake -f Makefile install
                      gmake[2]: Entering directory '/opt/qt5/qt5-build/qtbase/src/tools/bootstrap'
                      install -m 644 -p ../../../lib/libQt5Bootstrap.a /lib/libQt5Bootstrap.a
                      find: stat() error /lib/libQt5Bootstrap.a: No such file or directory
                      find: stat() error /bin/pod2man: Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS
                      find: stat() error /usr/bin/pod2man: Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS
                      find: cannot read dir /etc/sudoers.d: Permission denied
                      find: cannot read dir /etc/svc/volatile/critpid: Permission denied
                      
                      jsulmJ 1 Reply Last reply
                      0
                      • M Michele31415

                        I thought gmake install always had to be done as root. In any case, it works even less as ordinary user in qtbase:

                        /opt/qt5/qt5-build/qtbase $ gmake install
                        cd src/ && ( test -e Makefile || /opt/qt5/qt5-build/qtbase/bin/qmake -o Makefile /opt/qt5/qtbase/src/src.pro -qtconf /opt/qt5/qt5-build/qtbase/bin/qt.conf -- -opensource -nomake examples -nomake tests -platform solaris-g++ -skip qtserialbus ) && gmake -f Makefile install
                        gmake[1]: Entering directory '/opt/qt5/qt5-build/qtbase/src'
                        cd tools/bootstrap/ && ( test -e Makefile || /opt/qt5/qt5-build/qtbase/bin/qmake -o Makefile /opt/qt5/qtbase/src/tools/bootstrap/bootstrap.pro -qtconf /opt/qt5/qt5-build/qtbase/bin/qt.conf -- -opensource -nomake examples -nomake tests -platform solaris-g++ -skip qtserialbus ) && gmake -f Makefile install
                        gmake[2]: Entering directory '/opt/qt5/qt5-build/qtbase/src/tools/bootstrap'
                        install -m 644 -p ../../../lib/libQt5Bootstrap.a /lib/libQt5Bootstrap.a
                        find: stat() error /lib/libQt5Bootstrap.a: No such file or directory
                        find: stat() error /bin/pod2man: Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS
                        find: stat() error /usr/bin/pod2man: Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS
                        find: cannot read dir /etc/sudoers.d: Permission denied
                        find: cannot read dir /etc/svc/volatile/critpid: Permission denied
                        
                        jsulmJ Offline
                        jsulmJ Offline
                        jsulm
                        Lifetime Qt Champion
                        wrote on last edited by jsulm
                        #62

                        @Michele31415 said in QT5 build: CC: No such file or directory:

                        I thought gmake install always had to be done as root

                        Only when installing into system directories only writable by root.

                        https://forum.qt.io/topic/113070/qt-code-of-conduct

                        1 Reply Last reply
                        0
                        • SGaistS Offline
                          SGaistS Offline
                          SGaist
                          Lifetime Qt Champion
                          wrote on last edited by
                          #63

                          Sorry, I managed to miss a part of my answer. You should put the sources somewhere in your standard user home folder and do the build there. Then when it's done successfully you can install it and then do it as root if you want it in a system folder. Otherwise, if it's just for your user, you can install it somewhere in your user home folder.

                          Interested in AI ? www.idiap.ch
                          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                          1 Reply Last reply
                          0
                          • M Offline
                            M Offline
                            Michele31415
                            wrote on last edited by
                            #64

                            I guess I don't understand. I'm the only user. I always use /opt for big projects like QT or QEMU. The last thing I did was:

                            /opt/qt5/qt5-build/qtbase $ gmake -j16  > build.log 2>&1
                            

                            and that completed with no errors. So do I now have a working Qt5 in /opt/Qt5 that I can call from other builds? (QT5 is a prerequisite for the OpenSCAD 3D modeler).
                            The "Building Qt5 from Git" web page says that after doing gmake you should do gmake install. Can I just go ahead and use Qt without doing the install? How do I tell if it's working?

                            1 Reply Last reply
                            0
                            • SGaistS Offline
                              SGaistS Offline
                              SGaist
                              Lifetime Qt Champion
                              wrote on last edited by
                              #65

                              Unless you created a developer build you have to call make install in order to have everything in the right place. Since you have already configured everything else you can go on in each required sub directory and call make/make install.

                              If the modules are note configured, you can use the classic qmake/make/make install.

                              Interested in AI ? www.idiap.ch
                              Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                              1 Reply Last reply
                              0
                              • M Offline
                                M Offline
                                Michele31415
                                wrote on last edited by
                                #66

                                OK, so I say:

                                /opt/qt5/qt5-build/qtbase $ gmake
                                ...
                                (tail follows)
                                gmake[1]: Leaving directory '/opt/qt5/qt5-build/qtbase/qmake'
                                cd doc/ && ( test -e Makefile || /opt/qt5/qt5-build/qtbase/bin/qmake -o Makefile /opt/qt5/qtbase/doc/doc.pro -qtconf /opt/qt5/qt5-build/qtbase/bin/qt.conf -- -opensource -nomake examples -nomake tests -platform solaris-g++ -skip qtserialbus ) && gmake -f Makefile 
                                gmake[1]: Entering directory '/opt/qt5/qt5-build/qtbase/doc'
                                gmake[1]: Nothing to be done for 'first'.
                                gmake[1]: Leaving directory '/opt/qt5/qt5-build/qtbase/doc'
                                

                                and then

                                /opt/qt5/qt5-build/qtbase $ gmake install
                                cd src/ && ( test -e Makefile || /opt/qt5/qt5-build/qtbase/bin/qmake -o Makefile /opt/qt5/qtbase/src/src.pro -qtconf /opt/qt5/qt5-build/qtbase/bin/qt.conf -- -opensource -nomake examples -nomake tests -platform solaris-g++ -skip qtserialbus ) && gmake -f Makefile install
                                gmake[1]: Entering directory '/opt/qt5/qt5-build/qtbase/src'
                                cd tools/bootstrap/ && ( test -e Makefile || /opt/qt5/qt5-build/qtbase/bin/qmake -o Makefile /opt/qt5/qtbase/src/tools/bootstrap/bootstrap.pro -qtconf /opt/qt5/qt5-build/qtbase/bin/qt.conf -- -opensource -nomake examples -nomake tests -platform solaris-g++ -skip qtserialbus ) && gmake -f Makefile install
                                gmake[2]: Entering directory '/opt/qt5/qt5-build/qtbase/src/tools/bootstrap'
                                install -m 644 -p ../../../lib/libQt5Bootstrap.a /lib/libQt5Bootstrap.a
                                find: stat() error /lib/libQt5Bootstrap.a: No such file or directory
                                find: stat() error /bin/pod2man: Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS
                                find: stat() error /usr/bin/pod2man: Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS
                                find: cannot read dir /etc/sudoers.d: Permission denied
                                find: cannot read dir /etc/svc/volatile/critpid: Permission denied
                                find: cannot read dir /etc/svc/volatile/cups/certs: Permission denied
                                find: cannot read dir /etc/svc/volatile/sstore: Permission denied
                                find: cannot read dir /etc/svc/volatile/gdm: Permission denied
                                (and on and on)
                                
                                1 Reply Last reply
                                0
                                • SGaistS Offline
                                  SGaistS Offline
                                  SGaist
                                  Lifetime Qt Champion
                                  wrote on last edited by
                                  #67

                                  I don't understand why files in /etc are being accessed.

                                  Do you have the same issue if you build Qt in a standard user home folder ?

                                  Interested in AI ? www.idiap.ch
                                  Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                                  M 1 Reply Last reply
                                  0
                                  • SGaistS SGaist

                                    I don't understand why files in /etc are being accessed.

                                    Do you have the same issue if you build Qt in a standard user home folder ?

                                    M Offline
                                    M Offline
                                    Michele31415
                                    wrote on last edited by
                                    #68

                                    @SGaist No, I have not tried building it from my directory in /export/home/. I'm not really sure why that would give a different result. I'm the only user on the machine.

                                    M 1 Reply Last reply
                                    0
                                    • M Michele31415

                                      @SGaist No, I have not tried building it from my directory in /export/home/. I'm not really sure why that would give a different result. I'm the only user on the machine.

                                      M Offline
                                      M Offline
                                      Michele31415
                                      wrote on last edited by
                                      #69

                                      OK, I believe I have now successfully installed Qt5 in Solaris 11.4 SPARC. Referring to the above failed gmake install, there were three different things going on.

                                      1. /lib/libQt5Bootstrap.a not found. So I did
                                      ln -s /opt/qt5/qt5-build/qtbase/lib/libQt5Bootstrap.a /lib/libQt5Bootstrap.a
                                      
                                      1. /usr/bin/pod2man was a symbolic link pointing to itself (that's weird). So in /usr/bin I said
                                      rm pod2man
                                      ln -s /usr/perl5/5.26/bin/pod2man pod2man
                                      
                                      1. All the "cycles found" errors (not shown above) were because gmake install was using /usr/bin/install instead of /opt/csw/bin/install. So I said
                                      cd /opt/csw/bin
                                      ln -s ginstall install
                                      

                                      After those changes,

                                      # /opt/qt5/qt5-build/gmake install
                                      

                                      worked fine.

                                      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