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

Provide parsen for Sun Studio C++ compiler

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • warnings-plugin
    • None
    • Platform: All, OS: All

    Description

      Please provide parser for sun studio c++ compiler

      A few lines of example warnings

      "usi_plugin.cpp", line 212: Warning, badargtypel2w: String literal converted to
      char* in formal argument 1 in call to userlog(char*, ...).
      "usi_plugin.cpp", line 224: Warning, badargtypel2w: String literal converted to
      char* in formal argument msg in call to except(char*).

      "ServerList.cpp", line 8: Warning, badargtypel2w: String literal converted to
      char* in formal argument 1 in call to userlog(char*, ...).
      "ServerList.cpp", line 44: Warning, badargtypel2w: String literal converted to
      char* in formal argument 1 in call to userlog(char*, ...).
      "ServerList.cpp", line 50: Warning, badargtypel2w: String literal converted to
      char* in formal argument 1 in call to userlog(char*, ...).
      3 Warning(s) detected.

      Attachments

        Activity

          drulli Ulli Hafner added a comment -

          That should be quite easy.

          Is there an option in the compiler to produce qualified paths? Or is the
          filename relative to the root of the workspace? Without a qualified or workspace
          relative path the linking to the source files will not work.

          drulli Ulli Hafner added a comment - That should be quite easy. Is there an option in the compiler to produce qualified paths? Or is the filename relative to the root of the workspace? Without a qualified or workspace relative path the linking to the source files will not work.
          drulli Ulli Hafner added a comment -

          Fixed in HEAD.

          drulli Ulli Hafner added a comment - Fixed in HEAD.
          lynggaard lynggaard added a comment -

          > Is there an option in the compiler to produce qualified paths?

          I don't really know, I just grabed some output from our console log

          > Or is the filename relative to the root of the workspace?

          I guess it currently is, but the thing we c++ compile is no little that all
          source files are in the same directory

          > Without a qualified or workspace relative path the linking to the source files
          will not work.

          The links doesn't work for us as this is a slave build, but I guess that is
          another defect ?

          Thanx for the quick fix

          lynggaard lynggaard added a comment - > Is there an option in the compiler to produce qualified paths? I don't really know, I just grabed some output from our console log > Or is the filename relative to the root of the workspace? I guess it currently is, but the thing we c++ compile is no little that all source files are in the same directory > Without a qualified or workspace relative path the linking to the source files will not work. The links doesn't work for us as this is a slave build, but I guess that is another defect ? Thanx for the quick fix
          drulli Ulli Hafner added a comment -

          Links to sources that are build on a slave are indeed not yet supported (see
          issue 1749).

          drulli Ulli Hafner added a comment - Links to sources that are build on a slave are indeed not yet supported (see issue 1749).

          People

            drulli Ulli Hafner
            lynggaard lynggaard
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: