This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error: C9932E: Cannot obtain license for Compiler (feature compiler5) with license version >= 5.0201311

Hi,

I have downloaded ds-5 evaluation version and license from silver.arm.com yesterday.

I have tried 'armcc', it complain about the license (please see the 1st column table)

but, I have copied the license file into c:\tools\DS-5\license\ds5-eval.license.lic.

What should I check to fix this?

My test environment:

  • I am using Windows Console (cmd.exe) not using Eclipse.
  • Windows7 - the detail information is attached.
  • My configuration information is in 2nd column of the table
error message:

Product: ARM Compiler 5.04

Component: ARM Compiler 5.04

Tool: armcc [5040027]

Error: C9932E: Cannot obtain license for Compiler (feature compiler5) with license version >= 5.0201311

No such feature exists.

Feature:       compiler5

License path:  C:\Program Files\ARM\Licenses\license_HPE#3.dat;c:\DevEnv\license\license.lic;C:\tools\DS-5\license\ds5-eval.lice

nse.lic;

FLEXnet Licensing error:-5,357

For further information, refer to the FLEXnet Licensing documentation,

available at "www.flexerasoftware.com".

Cannot obtain license for Compiler (feature bsp_compiler5) with license version >= 5.0201311

No such feature exists.

Feature:       bsp_compiler5

License path:  C:\Program Files\ARM\Licenses\license_HPE#3.dat;c:\DevEnv\license\license.lic;C:\tools\DS-5\license\ds5-eval.lice

nse.lic;

FLEXnet Licensing error:-5,357

For further information, refer to the FLEXnet Licensing documentation,

available at "www.flexerasoftware.com".

ARMBIN=C:\tools\DS-5\bin

ARMBIN_ARMSD=C:\Program Files\ARM\RDI\armsd\1.3.1\66\win_32-pentium\armsd.exe

ARMBIN_AXD=C:\Program Files\ARM\RDI\AXD\1.3.1\98\win_32-pentium\axd.exe

ARMBIN_PRJ2XML=C:\Program Files\ARM\IDEs\CodeWarrior\RVPlugins\1.0\86\win_32-pentium\converters\RVD\prj2xml.exe

ARMCONF=C:\tools\DS-5\bin

ARMDLL=C:\tools\DS-5\bin

ARMHOME=c:\DevEnv\ads12\848

ARMINC=C:\tools\DS-5\include

ARMINCLUDE=C:\tools\DS-5\include

ARMLIB=C:\tools\DS-5\lib

ARMLMD_LICENSE_FILE=C:\Program Files\ARM\Licenses\license_HPE#3.dat;c:\DevEnv\license\license.lic

ARMROOT=C:\tools\DS-5

ARM_COMPILER_PATH=C:\tools\DS-5\bin

COMPUTERNAME=DH07-LAP02

LM_LICENSE_FILE=C:\tools\DS-5\license\ds5-eval.license.lic

Parents
  • When I use the 'DS5 Command Prompt' installed instead, the license issue was disappeared.

    And when I use Windows Console instead,

    I need to put the flag

    armcc --tool_variant=ds5eval

    in the release note, I found the below description.

    Header 1
    When the license and toolkit are configured within Eclipse then all license managed components will pick up the license and toolkit settings correctly, both within Eclipse and within the provided DS-5 Command Prompt (Windows) or suite_exec shell (Linux). If you use a different console then you must configure the tools manually. To do this set the environment variable ARMLMD_LICENSE_FILE to point at your license file, and ensure that the license managed compilation tools (armcc, armasm, armlink and fromelf) are passed the option --tool_variant=<toolkit> on each invocation. The argument to tool_variant is the type of license to use and corresponds to the prefix used by the license features in your license file up to the first '_' character. For example, if your license file contains a feature named "ds5eval_compiler5" then you must pass the compilation tools the --tool_variant=ds5eval option. Failure to set either the license location or the toolkit can result in errors reporting a failure to checkout a license, for example "Cannot obtain license for..."
Reply
  • When I use the 'DS5 Command Prompt' installed instead, the license issue was disappeared.

    And when I use Windows Console instead,

    I need to put the flag

    armcc --tool_variant=ds5eval

    in the release note, I found the below description.

    Header 1
    When the license and toolkit are configured within Eclipse then all license managed components will pick up the license and toolkit settings correctly, both within Eclipse and within the provided DS-5 Command Prompt (Windows) or suite_exec shell (Linux). If you use a different console then you must configure the tools manually. To do this set the environment variable ARMLMD_LICENSE_FILE to point at your license file, and ensure that the license managed compilation tools (armcc, armasm, armlink and fromelf) are passed the option --tool_variant=<toolkit> on each invocation. The argument to tool_variant is the type of license to use and corresponds to the prefix used by the license features in your license file up to the first '_' character. For example, if your license file contains a feature named "ds5eval_compiler5" then you must pass the compilation tools the --tool_variant=ds5eval option. Failure to set either the license location or the toolkit can result in errors reporting a failure to checkout a license, for example "Cannot obtain license for..."
Children
No data