Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-62991

Jenkins job for failing due to local libraries

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • _unsorted
    • Ubuntu 18.04, with jenkins version 2.222.4 and openJDK (1.8.0_252-8u252-b09-1~18.04-b09)

      Hi, 

      As i mentioned i have jenkins on Ubuntu 18.04 and I am able to configure jobs for C, Qt aplications(Desktop) and works fine with this requirement but when i want create jobs to build Qt WebAssembly, make fails due to some absulute path issues for more info please refer below summary

      WARNING root: -I or -L of an absolute path "-I/home/kmb/Qt/5.14.0/wasm_32/include" encountered. If this is to a local system header/library, it may cause problems (local system files make sense for compiling natively on your system, but not necessarily to JavaScript). Pass '-Wno-warn-absolute-paths' to emcc to hide this warning.
      WARNING root: Disabling asm.js validation for memory growth (memory can grow, but you lose some amount of speed)
      em++ -pipe -O3 -std=gnu++11 -s ALLOW_MEMORY_GROWTH=1 -Wall -Wextra -dM -E -o moc_predefs.h /home/kmb/Qt/5.14.0/wasm_32/mkspecs/features/data/dummy.cpp
      clang: error: no such file or directory: 'ALLOW_MEMORY_GROWTH=1'
      Makefile:870: recipe for target 'moc_predefs.h' failed
      make: *** [moc_predefs.h] Error 1
      Build step 'Execute shell' marked build as failure
      Finished: FAILURE

          [JENKINS-62991] Jenkins job for failing due to local libraries

          Mark Waite added a comment -

          This is not a Jenkins issue. The compiler clang believes that it should be able to find a file named ALLOW_MEMORY_GROWTH=1. That does not seem like a likely file name, so it probably indicates that you're using an incorrect command line argument.

          Mark Waite added a comment - This is not a Jenkins issue. The compiler clang believes that it should be able to find a file named ALLOW_MEMORY_GROWTH=1 . That does not seem like a likely file name, so it probably indicates that you're using an incorrect command line argument.

          Kallappa Bachagundi added a comment - - edited

          Thanks Mark,

          As said above, its not Jenkins issue, Its because of Environement variables and Shell selection
          Just added #!/bin/bash at first line followed by source command to set environement variable.

          that solves my problem

          Thanks

          Kallappa Bachagundi added a comment - - edited Thanks Mark, As said above, its not Jenkins issue, Its because of Environement variables and Shell selection Just added #!/bin/bash at first line followed by source command to set environement variable. that solves my problem Thanks

            Unassigned Unassigned
            kallappambk Kallappa Bachagundi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: